Quoting Måns Rullgård <mru@kth.se>: > Chris Doherty <chris.doherty@adelaide.edu.au> writes: > > > I've been using LVM happily for several months without any > > complaints or problems. This morning that all changed. The boot > > process stopped cold when lvm-mod (w|c)ouldn't load. My first > > impulse was to fsck, which I did as a matter of course. Eventually, > > I stumbled across what appears to be the source of my problem: > > > > root@connect4:~# ls -la /dev/lvm > > ?---rws-w- 8306 840966198 976250230 875573298 Sep 24 2004 /dev/lvm > > Your filesystem seems to have taken some heavy blows. You should fsck > it properly. You might need the -f flag to fsck to force a complete > check if filesystem is marked clean. the filesystem can't be mounted (which is the really worrying part) so i can't fsck it. root@connect4:~# mount -t ext3 /dev/vg1/lv1 /data mount: /dev/vg1/lv1 is not a valid block device root@connect4:~# ls /dev/vg1/ total 124 dr-xr-xr-x 2 root root 4096 Feb 6 18:46 ./ drwxr-xr-x 22 root root 118784 Feb 8 14:19 ../ crw-r----- 1 root disk 109, 0 Feb 6 18:46 group brw-rw---- 1 root disk 58, 0 Feb 6 18:46 lv1 the fsck that i mentioned previously was run on the other (available) filesystems, thinking that perhaps the LVM binaries (or some other related tool) had been corrupted. > -- > Måns Rullgård > mru@kth.se _______________________________________________ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
