[opensuse] lvm snapshot status inactive?
Can anyone explain to me what this means and why I had to manually activate this (and one other) snapshot after a reboot: --- Logical volume --- LV Name /dev/hostsuisse/taggart24r VG Name hostsuisse LV UUID MkQqKq-Pqcb-EFK1-d7y5-SzOq-qdpb-w24NqK LV Write Access read/write LV snapshot status INACTIVE destination for /dev/hostsuisse/taggart24r_vorigin LV Status NOT available LV Size 100.00 GiB Current LE 25600 COW-table size 10.00 GiB COW-table LE 2560 Snapshot chunk size 4.00 KiB Segments 1 Allocation inherit Read ahead sectors auto Thanks. -- Per Jessen, Zürich (12.8°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 22.10.2013 11:17, Per Jessen wrote:
Can anyone explain to me what this means and why I had to manually activate this (and one other) snapshot after a reboot:
--- Logical volume --- LV Name /dev/hostsuisse/taggart24r VG Name hostsuisse LV UUID MkQqKq-Pqcb-EFK1-d7y5-SzOq-qdpb-w24NqK LV Write Access read/write LV snapshot status INACTIVE destination for /dev/hostsuisse/taggart24r_vorigin LV Status NOT available LV Size 100.00 GiB Current LE 25600 COW-table size 10.00 GiB COW-table LE 2560 Snapshot chunk size 4.00 KiB Segments 1 Allocation inherit Read ahead sectors auto
Perhaps you had made more changes to the original LV than the snapshot could hold? What does 'lvs <VG name>' show in your system? A quick test in mine with a full 100M snapshot of home: darkside:~ # lvs sys /dev/sys/home-snap: read failed after 0 of 4096 at 42945413120: Input/output error /dev/sys/home-snap: read failed after 0 of 4096 at 42945470464: Input/output error /dev/sys/home-snap: read failed after 0 of 4096 at 0: Input/output error /dev/sys/home-snap: read failed after 0 of 4096 at 4096: Input/output error LV VG Attr LSize Pool Origin Data% Move Log Copy% Convert home sys owi-aos-- 40.00g home-snap sys swi-I-s-- 100.00m home 100.00 root sys -wi-ao--- 20.00g tmp sys -wi-ao--- 10.00g var sys -wi-ao--- 10.00g darkside:~ # darkside:~ # lvdisplay sys/home-snap /dev/sys/home-snap: read failed after 0 of 4096 at 42945413120: Input/output error /dev/sys/home-snap: read failed after 0 of 4096 at 42945470464: Input/output error /dev/sys/home-snap: read failed after 0 of 4096 at 0: Input/output error /dev/sys/home-snap: read failed after 0 of 4096 at 4096: Input/output error --- Logical volume --- LV Path /dev/sys/home-snap LV Name home-snap VG Name sys LV UUID QwG4O9-1gFV-C3s3-TDI2-SMqU-k5yH-TG01Rf LV Write Access read/write LV Creation host, time darkside.localnet, 2013-10-24 21:14:40 +0300 LV snapshot status INACTIVE destination for home LV Status available # open 0 LV Size 40.00 GiB Current LE 10239 COW-table size 100.00 MiB COW-table LE 25 Snapshot chunk size 4.00 KiB Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:17 Didn't get the 'NOT available' LV status though, not even after reboot. -- Martti -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Martti Laaksonen wrote:
On 22.10.2013 11:17, Per Jessen wrote:
Can anyone explain to me what this means and why I had to manually activate this (and one other) snapshot after a reboot:
--- Logical volume --- LV Name /dev/hostsuisse/taggart24r VG Name hostsuisse LV UUID MkQqKq-Pqcb-EFK1-d7y5-SzOq-qdpb-w24NqK LV Write Access read/write LV snapshot status INACTIVE destination for /dev/hostsuisse/taggart24r_vorigin LV Status NOT available LV Size 100.00 GiB Current LE 25600 COW-table size 10.00 GiB COW-table LE 2560 Snapshot chunk size 4.00 KiB Segments 1 Allocation inherit Read ahead sectors auto
Perhaps you had made more changes to the original LV than the snapshot could hold?
I don't think so, all I had to do was "lvchange -ay" to activate it. I suspect something weird in the LVM boot-up process.
What does 'lvs <VG name>' show in your system?
# lvs hostsuisse LV VG Attr LSize Origin Snap% Move Log Copy% Convert datahost hostsuisse -wi-ao 250.00g midsomer233r hostsuisse swi-a- 10.00g [midsomer233r_vorigin] 48.25 openSUSE hostsuisse -wi-ao 2.00t taggart2 hostsuisse -wi-ao 10.00g taggart24r hostsuisse swi-ao 10.00g [taggart24r_vorigin] 37.16 -- Per Jessen, Zürich (11.6°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 24.10.2013 22:02, Per Jessen wrote:
I don't think so, all I had to do was "lvchange -ay" to activate it. I suspect something weird in the LVM boot-up process.
Either that or the LV was already "broken" before reboot. Only logs may tell.
What does 'lvs <VG name>' show in your system?
# lvs hostsuisse LV VG Attr LSize Origin Snap% Move Log Copy% Convert datahost hostsuisse -wi-ao 250.00g midsomer233r hostsuisse swi-a- 10.00g [midsomer233r_vorigin] 48.25 openSUSE hostsuisse -wi-ao 2.00t taggart2 hostsuisse -wi-ao 10.00g taggart24r hostsuisse swi-ao 10.00g [taggart24r_vorigin] 37.16
This puzzles me, where are the origin LVs of the two snapshots in the above output? -- Martti -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Martti Laaksonen wrote:
On 24.10.2013 22:02, Per Jessen wrote:
I don't think so, all I had to do was "lvchange -ay" to activate it. I suspect something weird in the LVM boot-up process.
Either that or the LV was already "broken" before reboot. Only logs may tell.
I keep all logs for 5 years, where&what should I look for? This box was rebooted only about 3 weeks ago.
What does 'lvs <VG name>' show in your system?
# lvs hostsuisse LV VG Attr LSize Origin Snap% Move Log Copy% Convert datahost hostsuisse -wi-ao 250.00g midsomer233r hostsuisse swi-a- 10.00g [midsomer233r_vorigin] 48.25 openSUSE hostsuisse -wi-ao 2.00t taggart2 hostsuisse -wi-ao 10.00g taggart24r hostsuisse swi-ao 10.00g [taggart24r_vorigin] 37.16
This puzzles me, where are the origin LVs of the two snapshots in the above output?
Those are sparse LVs, created like this: lvcreate --virtualsize 1T --size 100M --name sparse vg1 -- Per Jessen, Zürich (12.9°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 25.10.2013 21:39, Per Jessen wrote:
I keep all logs for 5 years, where&what should I look for? This box was rebooted only about 3 weeks ago.
Well, I would first look for anything LVM (or device mapper) related in /var/log/messages and maybe in /var/log/boot.log. For example, I got this when the test snapshot I made became full: Oct 24 21:29:26 darkside.localnet lvm[1085]: Snapshot sys-home--snap is now 83% full. Oct 24 21:30:26 darkside.localnet lvm[1085]: Snapshot sys-home--snap is now 85% full. Oct 24 21:31:20 darkside.localnet kernel: device-mapper: snapshots: Invalidating snapshot: Unable to allocate exception. and after reboot: Oct 24 21:39:55 darkside.localnet kernel: device-mapper: snapshots: Snapshot is marked invalid. Oct 24 21:39:55 darkside.localnet lvm[1080]: Monitoring snapshot sys-home--snap Oct 24 21:39:55 darkside.localnet boot.lvm[1027]: 5 logical volume(s) in volume group "sys" now active Oct 24 21:39:55 darkside.localnet kernel: Buffer I/O error on device dm-17, logical block 10484720 Oct 24 21:39:55 darkside.localnet kernel: Buffer I/O error on device dm-17, logical block 10484720 Oct 24 21:39:55 darkside.localnet kernel: Buffer I/O error on device dm-17, logical block 10484734 In your case I would probably first check the log entries after the last reboot. If I couldn't find a reasonable explanation why the LV wasn't activated from those (e.g. timeout waiting for a device), I would start looking for entries before the reboot.
Those are sparse LVs, created like this:
lvcreate --virtualsize 1T --size 100M --name sparse vg1
Live and learn. It's been a while since I last read lvcreate man page. -- Martti -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (2)
-
Martti Laaksonen -
Per Jessen