[linux-lvm] lv inactive after reboot
Paul Jakma
paulj at itg.ie
Thu Oct 5 18:39:34 UTC 2000
hi,
I have an LV which i have made active with lvchange -ay, however after
a reboot it is inactive again (even though the rest of the LV's in
the VG start up fine with vgchange -ay).
the only difference between this LV and the rest that comes to mind is
that i had renamed it, and to do so i had to make the LV inactive.
what am i doing wrong?
[root at rossi /root]# lvdisplay /dev/Main_VG/games_xmame_lv
lvdisplay -- logical volume "/dev/Main_VG/games_xmame_lv" is not
active; try -D
[root at rossi /root]# lvdisplay -D /dev/Main_VG/games_xmame_lv
--- Logical volume ---
LV Name /dev/Main_VG/games_xmame_lv
VG Name Main_VG
LV Write Access read/write
LV Status NOT available
LV # 7
# open 0
LV Size 400 MB
Current LE 100
Allocated LE 100
Allocation next free
Read ahead sectors 120
Block device 58:6
[root at rossi /root]# fsck /dev/Main_VG/games_xmame_lv
Parallelizing fsck version 1.18 (11-Nov-1999)
e2fsck 1.18, 11-Nov-1999 for EXT2 FS 0.5b, 95/08/09
fsck.ext2: Operation not permitted while trying to open
/dev/Main_VG/games_xmame_lv
You must have r/w access to the filesystem or be root
[root at rossi /root]# mount /usr/lib/games/xmame
mount: permission denied
[root at rossi /root]# lvchange -ay /dev/Main_VG/games_xmame_lv
lvchange -- logical volume "/dev/Main_VG/games_xmame_lv" changed
lvchange -- doing automatic backup of volume group "Main_VG"
[root at rossi /root]# mount /usr/lib/games/xmame
<no error>
however on reboot, i will get the fsck "Op.. not permitted" error
because the LV isn't active. How do i make it permanently active
again???
regards,
paul jakma.
More information about the linux-lvm
mailing list