Bug#320312: Taking LVM snapshots can lead to an unuseable system
severity 320312 normal tags 320312 morinfo stop On Sat, Dec 17, 2005 at 03:46:58PM +0100, Bastian Blank wrote: > On Sat, Dec 17, 2005 at 03:32:58PM +0100, maximilian attems wrote: > > hmm i'm not shure it deserves the "critical" stamp. > > No it does not. The system can boot without a working /usr. downgraded > > anyway could you lvm2 maintainer look into that #320312. > > The referenced message refers to lvm 2.00.16, sarge ships with 2.01.04. > Also I see no output which describes what happened. > > Bastian thanks waldi for your input, can you still reproduce this bug with an up2date sarge system? if yes please describe how? regards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#320312: Taking LVM snapshots can lead to an unuseable system
On Sat, Dec 17, 2005 at 03:32:58PM +0100, maximilian attems wrote: > hmm i'm not shure it deserves the "critical" stamp. No it does not. The system can boot without a working /usr. > anyway could you lvm2 maintainer look into that #320312. The referenced message refers to lvm 2.00.16, sarge ships with 2.01.04. Also I see no output which describes what happened. Bastian -- A princess should not be afraid -- not with a brave knight to protect her. -- McCoy, "Shore Leave", stardate 3025.3 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#320312: Taking LVM snapshots can lead to an unuseable system
hmm i'm not shure it deserves the "critical" stamp. anyway could you lvm2 maintainer look into that #320312. thanks :) -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#320312: Taking LVM snapshots can lead to an unuseable system
Package: kernel-image-2.6.8-2-686 Version: 2.6.8-16 Severity: critical In sarge I was unable to take any lvm snapshots until I manually loaded the dm-snapshot kernel module with modprobe. I took a snapshot of my /usr filesystem, but didn't remove the snapshot with lvremove before rebooting. After reboot, not only is the snapshot unavailable, but also the original filesystem. This makes the system unusable until the snapshot can be removed. If I boot kernel-image-2.4.27-2-686, (which fortunately I also had installed), I don't need to manually load dm-snapshot. Perhaps this is an lvm bug instead? http://www.redhat.com/archives/dm-devel/2004-August/msg00015.html Many thanks, Alex
