>
> >
> > it basically says that an entry in that directory
> > does not fulfill some assertion (26638 % 4 = 2 != 0)
> >
> > I don't see how this would be linux-vserver related,
> > but if you try with 2.6.16-rc5 vanilla, it doesn't
> > happen?
> I have severall other parisc systems runing same kernel release on same kind
> of install (i.e. ext3 over sw raid1) and I never met such pb?
>
> > what does e2fsck say to that?
> >
> Weird:
> I umount fs and:
> # fsck /dev/md/root
> fsck 1.39-WIP (31-Dec-2005)
> e2fsck 1.39-WIP (31-Dec-2005)
> /dev/md/root: recovering journal
> /dev/md/root contains a file system with errors, check forced.
> 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/md/root: 85359/256000 files (2.1% non-contiguous), 325965/511968 blocks
> patst007:~ # ll /dev/md/root
> brw------- 1 root root 9, 2 Mar 16 11:21 /dev/md/root
> patst007:~ # ll /dev/md2
> brw-rw---- 1 root disk 9, 2 Jan 24 18:22 /dev/md2
>
> mmm?
>
Hello Herbert,
I just missed to test more.
In fact after this fsck, I was not any more able to mount this fs:
# mount /dev/md2 /DebSidRL
mount: /dev/md2 already mounted or /DebSidRL busy
To be sure, I check again the return code of this fsck:
# fsck -f /dev/md2 ; echo $?
fsck 1.39-WIP (31-Dec-2005)
e2fsck 1.39-WIP (31-Dec-2005)
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/md2: 85359/256000 files (2.1% non-contiguous), 325965/511968 blocks
0
But no more success:
# mount /dev/md2 /DebSidRL
mount: /dev/md2 already mounted or /DebSidRL busy
:<(
More sadely, at shutdown time, I can observe:
/dev/sda2 umounted^M
umount2: Device or resource busy^M
umount: /Develop: device is busy^M
umount2: Device or resource busy^M
umount: /Develop: device is busy^M
Unmounting local filesystems failed with error code 1.^M
Shutting down LVM Volume Groups... ^M
Can't deactivate volume group "vg_raid5" with 3 open logical volume(s)^M
Can't deactivate volume group "vg00" with 4 open logical volume(s)^M
Mounting root filesystem read-only...done.^M
Will now restart.^M
[331519.520000] md: stopping all md devices.^M
[331519.570000] md: md4 still in use.^M
[331519.610000] md: md1 switched to read-only mode.^M
[331519.660000] md: md2 still in use.^M
[331519.700000] md: md3 still in use.^M
[331519.740000] md: md0 still in use.^M
[331520.780000] Restarting system.^M
[331520.820000] .^M
Fortuantely, after the reboot (with 2.6.16-rc5-vs2.1.1-rc10-pa1-d32up) all
seems to come bak ok (startup script just did some successfull fsck).
Thanks,
Joel
PS: From location of this server, I don't have (as I would) access to irc
(just a annoying webmail interface), sorry.
_______________________________________________
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver
Received on Fri Mar 17 10:46:27 2006