public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Harry G McGavran Jr <w5pny@w5pny.com>
To: cygwin@cygwin.com
Subject: NTFS inode ouput from ls -i
Date: Tue, 18 Jul 2017 03:34:00 -0000	[thread overview]
Message-ID: <77d1bb70-5bce-0ac0-e011-1997f7db8a25@w5pny.com> (raw)

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?

Harry



--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

             reply	other threads:[~2017-07-17 17:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-18  3:34 Harry G McGavran Jr [this message]
2017-07-18 15:49 ` Corinna Vinschen
  -- 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=77d1bb70-5bce-0ac0-e011-1997f7db8a25@w5pny.com \
    --to=w5pny@w5pny.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).