Here is some further information about the
filesystem, produced by dumpe2fs. The blocks
being freed seem to be far outside the actual
filesystem.
The block numbers generated are not random,
the same blocks appear over and over again.
And for those of you into spooky numerology,
if you subtract (hex) 0x20000000 from all
the spurious block numbers, you get real block
numbers (ie. block numbers spread uniformly
over the range of real blocks). All this
suggests a rather scary hack - in ext2_free_blocks
we could just mask out 0x1FFFFFFF to derive
the block number before freeing it :->
Rich.
--------
dumpe2fs 1.12, 9-Jul-98 for EXT2 FS 0.5b, 95/08/09
Filesystem volume name: <none>
Last mounted on: <not available>
Filesystem UUID: c166f424-e1d6-11d2-9a73-004005a1eebd
Filesystem magic number: 0xEF53
Filesystem revision #: 0 (original)
Filesystem features: (none)
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 17415552
Block count: 17407872
Reserved block count: 870393
Free blocks: 16859367
Free inodes: 17415541
First block: 0
Block size: 4096
Fragment size: 4096
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 32736
Inode blocks per group: 1023
Last mount time: Wed Mar 24 15:17:05 1999
Last write time: Mon Mar 29 12:28:34 1999
Mount count: 0
Maximum mount count: 20
Last checked: Mon Mar 29 12:28:34 1999
Check interval: 15552000 (6 months)
Next check after: Sat Sep 25 12:28:34 1999
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
--
Bibliotech Ltd., 631-633 Fulham Rd., London SW6 5UQ. +44 171 460 4646
http://www.bibliotech.co.uk/ ------ Home page: http://www.annexia.org/
Work email: [EMAIL PROTECTED] ----- Home: [EMAIL PROTECTED]
Original message content Copyright � 1999 Richard Jones
