WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki
« previous next »
Pages: [1]   Go Down

Author Topic: LVM trouble  (Read 2335 times)

Offline Ztoragefool

  • Newbie
  • *
  • Posts: 27
LVM trouble
« on: November 16, 2010, 10:33:07 AM »
is there any magic involved to see lvm drives after rebooting? (TCL 3.2 64bit)

on creation, it appears as
 /dev/dm-0
 /dev/mapper/vg2-test -> ../dm-0
 /dev/vg2/test -> ../dm-0

but it´s gone after rebooting...
« Last Edit: November 16, 2010, 10:35:36 AM by Ztoragefool »
Logged

Offline gerald_clark

  • TinyCore Moderator
  • Hero Member
  • *****
  • Posts: 4254
Re: LVM trouble
« Reply #1 on: November 16, 2010, 10:41:33 AM »
You need to add the following line to /opt/bootlocal.sh and do a backup.
vgchange -ay
Logged

Offline Ztoragefool

  • Newbie
  • *
  • Posts: 27
Re: LVM trouble
« Reply #2 on: November 16, 2010, 10:54:39 AM »
worx! thanx!
Logged

Offline Ztoragefool

  • Newbie
  • *
  • Posts: 27
Re: LVM trouble
« Reply #3 on: November 17, 2010, 11:19:27 AM »
wowhowhooohohow...

bug? i just lost my volume.

atm i am playing around with qemu. starting my instance again, qemu complained one disk given did not exist. and qemu was right:

out of the sudden, my /dev/mapper contains nothing more than the control device. the symlinks are gone. but the /dev/dm-X devices they have shown at still exist.

ok, no prob, can handle this and reboot. but such things must not happen. so...

question: anyone wants to take the chance and investigate this further? any logs needed? dmesg and 3 files in /log/var do not show anything, so i´ve got nothing to post, but i need a coffe break anyway, so reboot can wait    8)

Logged
Pages: [1]   Go Up
« previous next »