From: Christian Hesse <list@eworm.de>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] lvm2 2.02.105 breaks snapshots
Date: Tue, 4 Feb 2014 09:55:44 +0100 [thread overview]
Message-ID: <20140204095544.65cad0f2@leda.localdomain> (raw)
In-Reply-To: <20140123142700.315e2d3f@leda.localdomain>
[-- Attachment #1: Type: text/plain, Size: 2118 bytes --]
Christian Hesse <list@eworm.de> on Thu, 2014/01/23 14:27:
> Hello everybody,
>
> looks like lvm2 2.02.105 breaks snapshots. This is my block device tree:
>
> NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
> sda 8:0 0 477G 0 disk
> |-sda1 8:1 0 767M 0 part
> | `-vg0-boot 254:0 0 64M 0 lvm /boot
> |-sda2 8:2 0 444,2G 0 part
> | `-cvg 254:3 0 444,2G 0 crypt
> | |-cvg-root 254:4 0 40G 0 lvm /
> | |-cvg-swap 254:5 0 4G 0 lvm [SWAP]
> | |-cvg-log 254:6 0 1G 0 lvm /var/log
> | `-cvg-home 254:8 0 320G 0 lvm /home
> |-sda3 8:3 0 32G 0 part
> `-sda128 259:0 0 1M 0 part
>
> Creating a snapshot succeeds, but it is broken and can not be mounted:
>
> # lvcreate -s -pr -l50%free -n snap-home cvg/home
> Logical volume "snap-home" created
> # mount /dev/cvg/snap-home /mnt/tmp
> mount: /dev/mapper/cvg-snap--home is write-protected, mounting read-only
> mount: wrong fs type, bad option, bad superblock on
> /dev/mapper/cvg-snap--home, missing codepage or helper program, or other
> error
>
> Syslog has a lot of these messages:
>
> [ 4823.002220] EXT4-fs (dm-7): ext4_check_descriptors: Checksum for group
> 256 failed (43470!=57954)
>
> Downgrading to lvm2 2.02.104 fixes the problem:
>
> # lvcreate -s -pr -l50%free -n snap-home
> cvg/home Logical volume "snap-home" created
> # mount /dev/cvg/snap-home /mnt/tmp
> mount: /dev/mapper/cvg-snap--home is write-protected, mounting read-only
>
> This is an Arch Linux system with Linux 3.12.8.
Hello everybody,
did anybody notice my mail? This is a real regression for me and I would like
to get this sorted. I will help with whatever is needed to find the problem.
--
main(a){char*c=/* Best regards, */"B?IJj;MEH"
"CX:;",b;for(a/* Chris get my mail address: */=0;b=c[a++];)
putchar(b-1/(/* gcc -o sig sig.c && ./sig */b/42*2-3)*42);}
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2014-02-04 8:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-23 13:27 [linux-lvm] lvm2 2.02.105 breaks snapshots Christian Hesse
2014-02-04 8:55 ` Christian Hesse [this message]
2014-02-04 16:47 ` Zdenek Kabelac
2014-02-06 14:48 ` Christian Hesse
2014-02-07 13:14 ` Christian Hesse
2014-02-07 23:36 ` [linux-lvm] blkid_wiping breaks snapshots (was: lvm2 2.02.105 breaks snapshots) Christian Hesse
2014-02-07 23:55 ` Christian Hesse
2014-02-10 8:33 ` [linux-lvm] blkid_wiping breaks snapshots Zdenek Kabelac
2014-02-10 9:30 ` Christian Hesse
2014-02-10 12:20 ` Zdenek Kabelac
2014-02-10 13:48 ` Christian Hesse
2014-02-10 14:12 ` Peter Rajnoha
2014-02-10 14:37 ` Christian Hesse
2014-02-10 15:56 ` Zdenek Kabelac
2014-02-10 18:15 ` Peter Rajnoha
2014-02-10 19:50 ` Zdenek Kabelac
2014-02-18 8:15 ` Christian Hesse
2014-02-18 8:27 ` Zdenek Kabelac
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140204095544.65cad0f2@leda.localdomain \
--to=list@eworm.de \
--cc=linux-lvm@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).