> I am running your program now over an hour without any corruption on the
> loopback mounted ext3 filesystem.
shit, I thought testing over an hour (10mins your program, umount, fsck -fD
test.img in a loop) is enough but it isn't. Damn f*ck :(
[email protected]:[/] # fsck -fD test.img
fsck 1.29 (24-Sep-2002)
e2fsck 1.29 (24-Sep-2002)
Truncating orphaned inode 6871 (uid=0, gid=0, mode=0103244, size=0)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Problem in HTREE directory inode 2 (/): bad block number 3291184.
Clear HTree index<y>? yes
Pass 3: Checking directory connectivity
/lost+found not found. Create<y>? yes
Pass 3A: Optimizing directories
Optimizing directories: 2
Pass 4: Checking reference counts
Pass 5: Checking group summary information
this occured just after I sent my first mail :((
PGP/GnuPG Key: 1024D/569DE2E3DB441A16
Fingerprint: 3469 0CF8 CA7E 0042 7824 080A 569D E2E3 DB44 1A16
Key available at http://www.keyserver.net. Encrypted e-mail preferred.
-----BEGIN PGP SIGNED MESSAGE-----
On September 29, 2002 10:19, Marc-Christian Petersen wrote:
> Hi Ryan,
> > I am running your program now over an hour without any corruption on the
> > loopback mounted ext3 filesystem.
> shit, I thought testing over an hour (10mins your program, umount, fsck -fD
> test.img in a loop) is enough but it isn't. Damn f*ck :(
Heh, I wonder why it happens faster here. I usually don't umount, and my
loopback filesystem is small enough that everything fits in RAM. Maybe my
Athlon XP 1800+ contributes to my computer's raw filesystem corruption power?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (GNU/Linux)
-----END PGP SIGNATURE-----