Ext3 users - Jul 2001 - broken ext3 fs after "poweroff" ext3 0.0.7a/2.2.19 wip 1.21

Hi,
after my X froze i had a fs inconsistency after the journal replay


[...]
EXT3-fs: 03:06: 1 orphan inode deleted
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 64k freed
INIT: version 2.78 booting
Loading /etc/console-tools/default.kmap.gz
Activating swap...
Adding Swap: 264560k swap-space (priority -1)
Checking root file system...
Parallelizing fsck version 1.21-WIP (01-Jun-2001)
/dev/hda6: clean, 6259/66264 files, 62137/264568 blocks
Calculating module dependencies... done.
Loading modules: usb-uhci usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
usb-uhci.c: $Revision: 1.237 $ time 20:08:12 Jun 15 2001
usb-uhci.c: High bandwidth mode enabled
PCI: Enabling bus mastering for device 00:3a
usb-uhci.c: USB UHCI at I/O 0x1860, IRQ 11
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 1
usb.c: USB new device connect, assigned device number 1
hub.c: USB hub found
hub.c: 2 ports detected
mousedev mice: PS/2 mouse device common for all mice
hid usb.c: registered new driver hid

Checking all file systems...
Parallelizing fsck version 1.21-WIP (01-Jun-2001)
/dev/hda7: recovering journal
/dev/hda7: clean, 41781/320640 files, 372115/640702 blocks
/dev/hda8: recovering journal
/dev/hda8: Clearing orphaned inode 96654 (uid=0, gid=0, mode=020600, size=0)
/dev/hda8: Already cleared block #0 (65025) found in orphaned inode 96654.
/dev/hda8 was not cleanly unmounted, check forced.
Deleted inode 96653 has zero dtime.  FIXED.
/dev/hda8: Inodes that were part of a corrupted orphan linked list found.

/dev/hda8: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
        (i.e., without -a or -p options)
/dev/hda9: recovering journal
/dev/hda9: clean, 27/128520 files, 24456/514048 blocks
/dev/hda10: recovering journal
/dev/hda10: clean, 197153/1921984 files, 3122257/3840472 blocks

fsck failed.  Please repair manually.

CONTROL-D will exit from this shell and continue system startup.

Give root password for maintenance
(or type Control-D for normal startup):
[...]


[...]
e2fsck 1.21-WIP, 01-Jun-2001 for EXT2 FS 0.5b, 95/08/09
Pass 1: Checking inodes, blocks, and sizes
Inodes that were part of a corrupted orphan linked list found.  Fix? yes

Inode 96654 was part of the orphaned inode list.  FIXED.
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences:  +65024 +65025
Fix? yes

Free blocks count wrong for group #1 (6696, counted=6694).
Fix? yes

Free blocks count wrong (65715, counted=65713).
Fix? yes

Inode bitmap differences:  -96653 -96654
Fix? yes

Free inodes count wrong for group #6 (14261, counted=14263).
Fix? yes

Free inodes count wrong (114098, counted=114100).
Fix? yes


/dev/hda8: ***** FILE SYSTEM WAS MODIFIED *****
/dev/hda8: 14668/128768 files (5.1% non-contiguous), 191319/257032 blocks
[...]

Flo
-- 
Florian Lohoff                  flo@rfc822.org             +49-5201-669912
     Why is it called "common sense" when nobody seems to have any?

Hi,

On Sat, Jul 07, 2001 at 03:12:15PM +0200, Florian Lohoff wrote:
 
> after my X froze i had a fs inconsistency after the journal replay
> 
> Checking all file systems...
> Parallelizing fsck version 1.21-WIP (01-Jun-2001)
> /dev/hda8: Clearing orphaned inode 96654 (uid=0, gid=0, mode=020600,
size=0)
							       ^^^^^^
Recovery error on a character device inode is a known bug in
e2fsprogs.  Fixed in e2fsprogs-1.22.

Cheers,
 Stephen

Florian Lohoff wrote:
> 
> Hi,
> after my X froze i had a fs inconsistency after the journal replay
> 
That's a bug in fsck.  e2fsprogs 1.22 fixes it.