[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Inconsistent ext3fs after crash (2.2.19/0.0.7a)



On Mon, Jun 18, 2001 at 08:07:58PM +1000, Andrew Morton wrote:
> 
> That won't test in-kernel recovery!  fsck will do its own recovery
> before mounting the fs.
> 
> My problem is that I don't have a separate /var, so /var is
> always recovered by the in-kernel recovery.  I'll set that up.
> 
> If it's not too much trouble, could you please boot with
> `init=/bin/sh', then mount /var by hand, then unmount it
> and run fsck?   Thanks.

*Urgs* Right - i didnt notice that the kernel didnt do a recovery
after the fsck did one but its obvious. Ok - here is the output.

It seems its an fsck bug:


[...]
 hda: hda1 hda2 < hda5 hda6 hda7 hda8 hda9 hda10 >
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.13)
apm: entry f000:43f2 cseg16 f000 dseg 40 cseg len ffff, dseg len ffff cseg16 len ffff
apm: Connection version 1.2
apm: AC on line, battery status high, battery life 100%
apm: battery flag 0x01, battery life unknown
EXT3-fs: WARNING: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
EXT3-fs: 03:06: orphan cleanup on read-only fs
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-2.03# mount -o remount,rw /
init-2.03# mount /var
EXT3-fs: 03:08: 3 orphan inodes deleted
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
init-2.03# umount /var
init-2.03# fsck.ext3 -yf /dev/hda8
e2fsck 1.21-WIP, 01-Jun-2001 for EXT2 FS 0.5b, 95/08/09
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/hda8: 8383/128768 files (0.8% non-contiguous), 92817/257032 blocks
init-2.03# setterm -dump



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





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]