[lkml]   [2004]   [May]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [BUG] 2.6.5 ntfs
    On Wed, 2004-05-05 at 13:32, Marcin Gibuła wrote:
    > > not be zero any more. Have you ever run memtest on your machine?
    > I'll try to do this.
    > > If you run "chkdsk /f" from windows on this partition, does it detect
    > > any errors?
    > It doesn't.


    > > dd if=~/mymftdump of=~/inode0x78a bs=1024 count=1 skip=1930
    > >
    > > And then email me the file ~/inode0x78a (this is only 1kiB in size).
    > Here it goes.

    Thanks. Analyzing this it is a highly fragmented file so it the $DATA
    attribute is spread over three more inodes. Could you email them to me,
    too please? They are 0x790 (= 1936), 0x791 (= 1937), and 0x792 (1938).

    You can get them like this (assuming you are using Bash as your shell):

    for i in 1936 1937 1938; do
    dd if=~/mymftdump of=~/inode$i bs=1024 count=1 skip=$i

    Once I have those I can uncompress the mapping pairs arrays in the data
    extents and ask you to capture the compressed data for me. It will be a
    simple script simillar to the above...

    Thanks a lot for your help.

    Best regards,

    Anton Altaparmakov <aia21 at> (replace at with @)
    Unix Support, Computing Service, University of Cambridge, CB2 3QH, UK
    Linux NTFS maintainer / IRC: #ntfs on
    WWW: &

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 14:02    [W:0.022 / U:21.368 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site