LVM 1: Snapshot causes seg fault of lvdisplay and crashes system
I did the following to create a snapshot of an active filesystem to try to make a consistent copy of it:
# lvcreate --extents 30 --snapshot --name home2snap /dev/sys/home2gb ... lvcreate -- INFO: using default snapshot chunk size of 64 KB for "/dev/sys/home\ 2snap" lvcreate -- doing automatic backup of "sys" lvcreate -- logical volume "/dev/sys/home2snap" successfully created
# lvdisplay /dev/sys/home2gb
--- Logical volume ---
LV Name /dev/sys/home2gb
VG Name sys
LV Write Access read/write
LV snapshot status source of
/dev/sys/home2snap [active]
Segmentation fault
# lvdisplay /dev/sys/home2gb
--- Logical volume ---
LV Name /dev/sys/home2gb
VG Name sys
LV Write Access read/write
LV snapshot status source of
/dev/sys/home2snap [active]
Segmentation fault
ecstasy:/#<At this point I lost my remote connection to the machine and presume it crashed; it probably didn't reboot, since subsequent attempts to reconnect via ssh failed and ping failed as well.>
The kernel is probably 1.0.3 (Debian SPARC sun4u 2.4.21 up) and the lvm tools are 1.0.8.
Any suggestions for avoiding these seg faults and the system crash?
Sincerely,
Ken Fuchs <[email protected]>
Quoted 28 lines · Ken Fuchs
I did the following to create a snapshot of an active filesystem to try to make a consistent copy of it:
# lvcreate --extents 30 --snapshot --name home2snap /dev/sys/home2gb ... lvcreate -- INFO: using default snapshot chunk size of 64 KB for "/dev/sys/home\ 2snap" lvcreate -- doing automatic backup of "sys" lvcreate -- logical volume "/dev/sys/home2snap" successfully created# lvdisplay /dev/sys/home2gb --- Logical volume --- LV Name /dev/sys/home2gb VG Name sys LV Write Access read/write LV snapshot status source of /dev/sys/home2snap [active] Segmentation fault # lvdisplay /dev/sys/home2gb --- Logical volume --- LV Name /dev/sys/home2gb VG Name sys LV Write Access read/write LV snapshot status source of /dev/sys/home2snap [active] Segmentation fault ecstasy:/#
Quoted 8 lines
<At this point I lost my remote connection to the machine and presume it crashed; it probably didn't reboot, since subsequent attempts to reconnect via ssh failed and ping failed as well.>
The kernel is probably 1.0.3 (Debian SPARC sun4u 2.4.21 up) and the lvm tools are 1.0.8.
Any suggestions for avoiding these seg faults and the system crash?
Upgrade to an actual driver LVM version. You hit a list bug IRT snapshots.
Quoted 10 lines
Sincerely,
Ken Fuchs <[email protected]>
_______________________________________________
linux-lvm mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
Signature · 15 lines
Regards,
Heinz -- The LVM Guy --
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Red Hat, Inc.
Consulting Development Engineer Am Sonnenhang 11
56242 Marienrachdorf
Germany
[email protected] +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-