On Mon, 21 Aug 2006, Szakacsits Szabolcs wrote: > On Mon, 21 Aug 2006, Frans Pop wrote: > > On Monday 21 August 2006 19:31, you wrote: > > > Would it be possible to send the vista metadata image > > > > Available from: http://people.debian.org/~fjp/ntfsmeta.img.bz2 > > > > > and tell us at what size you resize? Thanks. > > > > Mostly at 9GB but 12GB also fails. > > Resizing at 12 GB doesn't require any relocation: > > # ntfsresize -ns 12G vista-corruptions.img > ntfsresize v1.3.1 (libntfs 9:0:0) > Device name : vista-corruptions.img > NTFS volume version: 3.1 > Cluster size : 4096 bytes > Current volume size: 20971516416 bytes (20972 MB) > Current device size: 20971516416 bytes (20972 MB) > New volume size : 11999994368 bytes (12000 MB) > Checking filesystem consistency ... > 100.00 percent completed > Accounting clusters ... > Space in use : 7052 MB (33.6%) > Collecting resizing constraints ... > ==> Needed relocations : 0 (0 MB) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > Schedule chkdsk for NTFS consistency check at Windows boot time ... > Resetting $LogFile ... (this might take a while) > Updating $BadClust file ... > Updating $Bitmap file ... > Updating Boot record ... > The read-only test run ended successfully. > > So files can't become corrupted.
And resizing at 9 GB, only one file problematic file gets relocated, the other three aren't touched. If files would get randomly corrupted then the regression tests should catch them, and also more people would report file corruptions. I think you have a hardware problem. Szaka -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]