On Sun, 13 Nov 2005, Szakacsits Szabolcs wrote:
> On Sun, 13 Nov 2005, Anton Altaparmakov wrote:
> > On Sun, 13 Nov 2005, Szabolcs Szakacsits wrote:
> > That code was there before (well ok, code of equivalent functionality).
>
> Actually it wasn't exactly equivalent, only almost. That code always
> rounded up the mft size to cluster boundary, this one only if all system
> files fits into the first cluster. New, empty records are added also only
> in this case, not otherwise.
>
> In short none of us was right, the truth is between them.
Interesting! Well discovered! (-: I only ever tried 64k cluster size
and did the smaller ones by assumption. You obviously had done the
smaller one and did not see need to do it. Thanks for figuring it out
properly. (-:
> And this is what's left for mkntfs v3.1:
>
> Inode 0 attribute 0x30 content: DIFFER
> Inode 0 attribute 0x80 content: DIFFER
> Inode 1 attribute 0x80 content: DIFFER
> Inode 2 attribute 0x30 content: DIFFER
> Inode 2 attribute 0x80 length: 46153728 != 4194304
> Inode 4 attribute 0x30 content: DIFFER
> Inode 5 attribute 0x50 length: 4144 != 4608
> Inode 5 attribute 0xa0:$I30 content: DIFFER
> Inode 6 attribute 0x80 content: DIFFER
> Inode 7 attribute 0x80 content: DIFFER
> Inode 9 attribute 0x30 content: DIFFER
> Inode 9 attribute 0x80:$SDS length: 262396 != 262720
> Inode 9 attribute 0x90:$SDH length: 144 != 288
> Inode 9 attribute 0x90:$SII length: 128 != 248
> Inode 11 attribute 0x90:$I30 content: DIFFER
> Inode 24 attribute 0x90:$O content: DIFFER
> Inode 24 attribute 0x90:$Q content: DIFFER
Cool. The list is really shrinking nicely. Are the 0x30 differences just
timestamps or is there more to it?
Best regards,
Anton
--
Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @)
Unix Support, Computing Service, University of Cambridge, CB2 3QH, UK
Linux NTFS maintainer / IRC: #ntfs on irc.freenode.net
WWW: http://linux-ntfs.sf.net/ & http://www-stu.christs.cam.ac.uk/~aia21/
|