[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#419209: lvm2: Hangs during snapshot creation

Hash: SHA512


first of all, I raised the severity of the bug to critical as it makes
the whole system break. Also I add debian-devel to Cc as the bug is very
problematic and I wonder how lvm2 was able to get into lenny with that
big problem!

Also I am willing to help solving the bug. My next step will be to
import the whole version history to git and try to besect the problem.

First to my use of LVM.

I did use lvm1 with kernel 2.4 on etch for long time now using exact the
same procedure which trigger the problem right now. Then with the
release of lenny I start upgrading my stable systems. This involved a
kernel upgrade as lenny only runs with the very instable kernel tree 2.6
and upgrade of the lvm metadata.

A short test of the lvm snapshoots afterwards runs fine so I was not
care about this road works (Is that the correct expression for the
German "Baustelle"?). (I use snapshots every night in a script to backup
the system.)

Days after I noticed that apt-get install froze randomly and I had to
reboot the system with a power cycle (reboot didn't work). First I was
thinking about one of the many kernel bugs in 2.6 and tried the newest
kernel from kernel.org. But the bug was still there. After several days
I end in finding the problem in the LVM2 subsystem and two days later,
today, I found this ug report and was very shocked! If I had know of it
before I had never upgrade any of may stable systems to lenny! But now
one of them is sticked on lenny as I know no way to revert the LVM back
to LVM1.

So this bug is a complete show stopper for lenny!!!!

Am Sa den 14. Apr 2007 um 12:53 schrieb Jean-Luc Coulon (f5ibh):
> New lvm2 version (2.02.24) hangs during snapshot creation.
> The lvmvreate process is not killeable at this point and the system need to be
> reboted.

That is the correct description. But more over the system will be
unbootable at all! I have to run /etc/init.d/reboot stop by hand to hard
reboot the system. A normal shutdown will end in a hanging system with
no remote access at all. The only solution at that point is to
powercycle the machine which is very problematic with remote system.

Am Fr den  2. Nov 2007 um 16:21 schrieb Stefan Pfetzing:
> did you try to snapshot your /var? Because to me it seemms like the  
> current lvm2 configurations tries to use /var/lock/lvm for its locking 
> files, and this leads to a deadlock.

This is not really a problem as it is irrelevant if that file is locked
or not in the sapshoot.

Also the problem happens with random lvms not only with /var.

And I wonder why this should be a problem at all as the lvm1 was working
pretty stable for years now.

Am So den 30. Mär 2008 um 10:52 schrieb Bastian Blank:
> # Automatically generated email from bts, devscripts version 2.9.26
> severity 419209 important

The severity of this bug is absolute critical and not just important!

   Klaus Ethgen
- -- 
Klaus Ethgen                            http://www.ethgen.de/
pub  2048R/D1A4EDE5 2000-02-26 Klaus Ethgen <Klaus@Ethgen.de>
Fingerprint: D7 67 71 C4 99 A6 D4 FE  EA 40 30 57 3C 88 26 2B
Version: GnuPG v1.4.9 (GNU/Linux)


Reply to: