Re: kernel errors from a merging snapshot

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

 



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?

_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/




[Index of Archives]     [Gluster Users]     [Kernel Development]     [Linux Clusters]     [Device Mapper]     [Security]     [Bugtraq]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]

  Powered by Linux