linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: "Lentes, Bernd" <bernd.lentes@helmholtz-muenchen.de>
Cc: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] kernel errors from a merging snapshot
Date: Tue, 14 Oct 2014 17:07:17 -0400	[thread overview]
Message-ID: <20141014210717.GA19345@redhat.com> (raw)
In-Reply-To: <15785B7E063D464C86DD482FCAE4EBA501B7EB057A20@XCH11.scidom.de>

On Tue, Oct 14 2014 at  2:08pm -0400,
Lentes, Bernd <bernd.lentes@helmholtz-muenchen.de> wrote:

> Hi,
> 
> i have a /-filesystem residing on a lv. I also had a snapshot of that lv because I tried some software. After testing the software I merged the snapshot into the origin, by rebooting. It seemed to went fine.
> Btw: how do I know when merging is finished ? Where can I see results from the merging ?

You can use lvm to see the merge in progress (via lvs).  Or you can have
a look at the "How to determine when a merging is complete" section of
the kernel's Documentation/device-mapper/snapshot.txt

> But in /var/log/messages I have error messages about a block device:
> 
> Oct 14 16:22:45 vm59093-4 kernel: [    7.580247] Buffer I/O error on device dm-3, logical block 0
> Oct 14 16:22:45 vm59093-4 kernel: [    7.580254] Buffer I/O error on device dm-3, logical block 1
> Oct 14 16:22:45 vm59093-4 kernel: [    7.580258] Buffer I/O error on device dm-3, logical block 2
> Oct 14 16:22:45 vm59093-4 kernel: [    7.580261] Buffer I/O error on device dm-3, logical block 3
> Oct 14 16:22:45 vm59093-4 kernel: [    7.580264] Buffer I/O error on device dm-3, logical block 0
> Oct 14 16:22:45 vm59093-4 kernel: [    7.580271] Buffer I/O error on device dm-3, logical block 9961471
> Oct 14 16:22:45 vm59093-4 kernel: [    7.580274] Buffer I/O error on device dm-3, logical block 9961471
> Oct 14 16:22:45 vm59093-4 kernel: [    7.580341] Buffer I/O error on device dm-3, logical block 0
> Oct 14 16:22:45 vm59093-4 kernel: [    7.580345] Buffer I/O error on device dm-3, logical block 1
> 
> Dm-3 is the snapshot I merged (although I named it root-snapshot while creating, not root--snapshot !):
> 
> Dmsetup info says:
> 
> ...
> Name:              vg_1-root--snapshot
> State:             ACTIVE
> Read Ahead:        1024
> Tables present:    LIVE
> Open count:        0
> Event number:      0
> Major, minor:      252, 3
> Number of targets: 1
> UUID: LVM-ZfsXYr9bkOt1d9bMNpcrn7MxH2aX6H0bhELCnywHd7rbddry6f63xtkk1vqs1hvv
> ...
> 
> The errors appeared during the reboot. Is that normal ?

We replace the device that is being merged with the "error" target.  So
any IO directly to the merging device will get errored out.  But IIRC
that was fixed with an updated lvm2 (libdm) change to hide the device
from udev (udev rules were trying to read labels from the device via
blkid, etc).

Which distro and kernel are you using?

  reply	other threads:[~2014-10-14 21:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-14 18:08 [linux-lvm] kernel errors from a merging snapshot Lentes, Bernd
2014-10-14 21:07 ` Mike Snitzer [this message]
2014-10-15 18:53   ` Lentes, Bernd

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=20141014210717.GA19345@redhat.com \
    --to=snitzer@redhat.com \
    --cc=bernd.lentes@helmholtz-muenchen.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).