{"id":45,"date":"2006-04-09T19:53:58","date_gmt":"2006-04-09T17:53:58","guid":{"rendered":"http:\/\/blog.blackdown.de\/2006\/04\/09\/lvm-snapshots-with-debian-sarge-and-linux-2616\/"},"modified":"2016-10-29T03:51:01","modified_gmt":"2016-10-29T01:51:01","slug":"lvm-snapshots-with-debian-sarge-and-linux-2616","status":"publish","type":"post","link":"https:\/\/blackdown.de\/articles\/lvm-snapshots-with-debian-sarge-and-linux-2616\/","title":{"rendered":"LVM Snapshots With Debian Sarge and Linux 2.6.16"},"content":{"rendered":"

I have upgraded this server to kernel 2.6.16.2. The next backup cycle resulted in a minor disaster: The backup process deadlocked at removing the first LVM2<\/a> snapshot and the snapshot source volumes were blocking write accesses. A cleanup shutdown was impossible and I had to hard-reset the machine.<\/p>\n

After some searching I found out that you apparently<\/a> need lvm2 2.02.01 or later and devmapper 1.02.02 or later to successfully remove snapshot volumes now. Unfortunately neither of these versions is available for sarge from Debian or backports.org<\/a> yet, so I had to make my own backports.
\nAs it turned out (see below), it is also necessary to use 2.6.16.12 or to apply the patch from this email<\/a> to older 2.6.16 versions in order to reliably remove snapshots.<\/p>\n

If you are brave enough, you can get the backported packages by adding<\/p>\n

deb http:\/\/blog.blackdown.de\/static\/debian\/lvm\/ sarge main\r\ndeb-src http:\/\/blog.blackdown.de\/static\/debian\/lvm\/ sarge main<\/pre>\n
to \/etc\/apt\/sources.list<\/code>.<\/p>\n
The repository contains debs for devmapper, dlm, lvm2, and lvm-common. The Release<\/code> files is signed with my GPG key<\/a>. If you have a recent apt<\/code> version, you can authenticate the packages after importing the key with apt-key<\/code>:<\/p>\n
wget http:\/\/blog.blackdown.de\/static\/gpg.asc -O - | \\r\n    sudo apt-key add -<\/pre>\n
April 15th, 2006:<\/strong> In about 40 backup cycles I’ve seen<\/a> three lockups with 2.6.16.2 now. Until snapshots get fixed in 2.6.16, I’d recommend to stay with 2.6.15. I’m using 2.6.15.3 again now.<\/em><\/p>\n
April 24th, 2006:<\/strong> Added note about “dm snapshot: fix kcopyd destructor<\/a>” patch from Alasdair G Kergon. With this patch snapshots work fine for me again.<\/em><\/p>\n
May 2nd, 2006:<\/strong> Alasdair G Kergon’s patch has been included in 2.6.16.12.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"
I have upgraded this server to kernel 2.6.16.2. The next backup cycle resulted in a minor disaster: The backup process deadlocked at removing the first LVM2 snapshot and the snapshot source volumes were blocking write accesses. A cleanup shutdown was impossible and I had to hard-reset the machine. After some searching I found out that
[→ Read the rest of this entry<\/a>]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"spay_email":"","jetpack_publicize_message":"","jetpack_is_tweetstorm":false,"jetpack_publicize_feature_enabled":true},"categories":[3,2,12],"tags":[],"yoast_head":"\n\n\n\n\n\n\n\n\n\n\n\n\n\t\n\t\n\t\n