<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=us-ascii" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi Dave,<br>
<br>
David L. Anselmi wrote:
<blockquote cite="mid:4F597292.7060906@anselmi.us" type="cite">
<pre wrap=""><a class="moz-txt-link-abbreviated" href="mailto:dshaw@famece.com">dshaw@famece.com</a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">i.e., seemingly random files showing 2 hard links that couldn't be
confirmed by searching for those inode numbers.
</pre>
</blockquote>
<pre wrap=""><!---->
I wouldn't expect Linux to have anything meaningful to say about file system structures in NTFS.
What do you think the link count or inode numbers mean? I don't know so I wouldn't pay any
attention to them.
</pre>
</blockquote>
While I do agree with you that the Linux re-implementations of NTFS
probably are unlikely to say anything meaningful about the file system
structures in NTFS, I do remember that NTFS supports hard links and
there was even a set of POSIX tools available for Windows NT one of
which was LN.EXE that let you create hard links to a file. It did not
support symlinks and neither did NTFS, but if you created a hard link
then the link count would be incremented for both hard links to the
inode. I don't remember if they used the term inode but there was a
similar concept in NTFS.<br>
<br>
Jim<br>
<pre class="moz-signature" cols="72">--
Jim Ockers, P.E., P.Eng. (<a class="moz-txt-link-abbreviated" href="mailto:ockers@ockers.net">ockers@ockers.net</a>)
Contact info: <a class="moz-txt-link-freetext" href="http://www.ockers.net/">http://www.ockers.net/</a>
</pre>
</body>
</html>