On Mon, Nov 02, 2009 at 05:21:00PM +0100, Claus Herwig wrote: > Concerning the severity, citing debian policy > (http://www.debian.org/Bugs/Developer.en.html) > > critical > > makes unrelated software on the system (or the whole system) break, > > or causes serious data loss, or introduces a security hole on systems > > where you install the package. > Doubtlessly this is the case for more than one or two people. So please > stop playing the severity game and lets start fixing this bug. It's > original report is more than two years old now. Thank you.
This is up to the maintainer, something that have been explained already in this bug. > The machine which hangs has a significantly higher filesystem activity > on some of the volumes than the one which runs the snapshots ok. For now > this is the only significant difference I can produce. That is a good definition of a race condition. And a quick look around shows a Red Hat bug #496100[1], which references two commits that fixed it in 2.6.30. > > uname -a > Linux jake.checon.net 2.6.22.19-vs2.checon.elwood #1 SMP Fri Mar 13 > 23:16:22 CET 2009 x86_64 GNU/Linux > (vanilla kernel with vserver patch) This kernel is not even remotely within the waranty from Debian. Bastian [1]: https://bugzilla.redhat.com/show_bug.cgi?id=496100 -- Many Myths are based on truth -- Spock, "The Way to Eden", stardate 5832.3 -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
