From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: NTFS inode ouput from ls -i
Date: Tue, 18 Jul 2017 15:49:00 -0000 [thread overview]
Message-ID: <20170718095009.GB26902@calimero.vinschen.de> (raw)
In-Reply-To: <77d1bb70-5bce-0ac0-e011-1997f7db8a25@w5pny.com>
[-- Attachment #1: Type: text/plain, Size: 1996 bytes --]
On Jul 17 11:44, Harry G McGavran Jr wrote:
> I just had to deal with the output from chkdsk on my Windows 7 pro
> that lists MFT record numbers just like ifind and icat do
> in the Sleuth Kit as summarized in:
>
> https://cygwin.com/ml/cygwin/2012-11/msg00172.html
>
> The chkdsk MFT record numbers are exactly what ifind and icat
> display/use. I also discovered when doing "ls -i" on NTFS
> file systems mounted on my Ubuntu 16.04 linux system that
> the "ls -i" numbers reported are the same as the chkdsk, ifind, and icat
> record numbers. These are all the lower 32 bits of the 64 bit
> numbers reported by "ls -i" with the current cygwin. Had
> the cygwin "find -inum" and "ls -i" used these 32 bit numbers,
> my task would have been easier. From the above link, Corinna
> found it odd that ifind and icat would use the 32 bit numbers.
> I would have preferred them when dealing with chkdsk issues.
>
> What's the current thinking about this?
The descriptions I found describes the NTFS FileID as a combination
of the 16 bit sequence number with the 48 bit file record number(*).
Stripping off 16 bits sequence number would be ok, but stripping the
upper 16 bit from a 48 bit record number sounds bad.
OTOH, the maximum number of files on an NTFS volume is restricted
to the number of clusters, which is 2^32-1.
If it's *safe* to assume that the record number corresponds with
the cluster number, ok, but I'm not sure this is the case. I never
use really big filesystems with Windows. This would need testing.
But then there's another problem. The 64 bit file ID can also be
used to open a file by ID. Stripping the upper 32 bit from the
value disallows to use the file ID in that way.
Corinna
(*) http://digitalresidue.blogspot.de/2016/02/getting-started-with-sleuth-kit-pt-3.html
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-07-18 9:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-18 3:34 Harry G McGavran Jr
2017-07-18 15:49 ` Corinna Vinschen [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-07-18 22:57 Harry G McGavran Jr
2012-11-22 21:08 Michael Lester
2012-11-23 7:11 ` Peter Rosin
2012-11-23 12:21 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170718095009.GB26902@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).