From: Lee Rocky <rocky366@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Invalid new snapshot
Date: Thu, 15 Dec 2005 11:02:26 +0800 [thread overview]
Message-ID: <539807300512141902w3cfa6ecdk@mail.gmail.com> (raw)
In-Reply-To: <20051214145144.GO25866@agk.surrey.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 4662 bytes --]
Kernel => 2.6.13 (dm-snapshot-bio_list-fix.patch patched)
lvm version =>
LVM version: 2.02.01 (2005-11-23)
Library version: 1.02.02 (2005-12-02)
Driver version: 4.4.0
-bash-3.00# lvcreate -s -L3000 -n test2_1 /dev/VG01/test2
Rounding up size to full physical extent 2.94 GB
Logical volume "test2_1" created
-bash-3.00# lvcreate -s -L 3000 -n test2_2 /dev/VG01/test2
Rounding up size to full physical extent 2.94 GB
Logical volume "test2_2" created
-bash-3.00# lvcreate -s -L 3000 -n test2_3 /dev/VG01/test2
Rounding up size to full physical extent 2.94 GB
Logical volume "test2_3" created
lvs --segment -v
----------------------------------------------------------
Finding all logical volumes
/dev/VG01/test2_3: read failed after 0 of 4096 at 0: Input/output error
LV VG Attr Start SSize #Str Type Stripe
Chunk
lv1 VG01 -wi-ao 0 256.00M 1 linear 0 0
lv2 VG01 -wi-ao 0 1.00G 1 linear 0 0
lv3 VG01 -wi-a- 0 64.00M 1 linear 0 0
lv4 VG01 -wi-ao 0 512.00M 1 linear 0 0
lv5 VG01 -wi-ao 0 128.00M 1 linear 0 0
test2 VG01owi-ao 0 29.31G 1 linear 0 0
test2_1 VG01 swi-a- 0 2.94G 1 linear 0 8.00K
test2_2 VG01 swi-a- 0 2.94G 1 linear 0 8.00K
test2_3 VG01 Swi-I- 0 2.94G 1 linear 0 8.00K
-bash-3.00# lvs -a
/dev/VG01/test2_3: read failed after 0 of 4096 at 0: Inpu/output error
LV VG Attr LSize Origin Snap% Move Log Copy%
lv1 VG01 -wi-ao 256.00M
lv2 VG01 -wi-ao 1.00G
lv3 VG01 -wi-a- 64.00M
lv4 VG01 -wi-ao 512.00M
lv5 VG01 -wi-ao 128.00M
test2 VG01 owi-ao 29.31G
test2_1 VG01 swi-a- 2.94G test2 30.00
test2_2 VG01 swi-a- 2.94G test2 29.99
test2_3 VG01 Swi-I- 2.94G test2 100.00
lvscan
----------------------------------------------------------
/dev/VG01/test2_3: read failed after 0 of 4096 at 0: Input/output error
ACTIVE '/dev/VG01/lv1' [256.00 MB] inherit
ACTIVE '/dev/VG01/lv2' [1.00 GB] inherit
ACTIVE '/dev/VG01/lv3' [64.00 MB] inherit
ACTIVE '/dev/VG01/lv4' [512.00 MB] inherit
ACTIVE '/dev/VG01lv5' [128.00 MB] inherit
ACTIVE Original '/dev/VG01/test2' [29.31 GB] inherit
ACTIVE Snapshot '/dev/VG01/test2_1' [2.94 GB] inherit
ACTIVE Snapshot '/dev/VG01/test2_2' [2.94 GB] inherit
ACTIVE Snapshot '/dev/VG01/test2_3' [2.94 GB] inherit
dmesg after created
----------------------------------------------------------
attempt to access beyond end of device
dm-11: rw=17, want=2271285024, limit=6160384
device-mapper: Error reading/writing snapshot
device-mapper: snapshot is marked invalid
dmesg after tried to mount
----------------------------------------------------------
printk: 1 messages suppressed.
Buffer I/O error on device dm-12, logical block 0
Buffer I/O error on device dm-12, logical block 1
Buffer I/O error on device dm-12, logical block 2
Buffer I/O error on device dm-12, logical block 3
Buffer I/O error on device dm-12, logical block 4
Buffer I/O error on device dm-12, logical block 5
Buffer I/O error on device dm-12, logical block 6
Buffer I/O error on device dm-12, logical block 7
Buffer I/O error on device dm-12, logical block 0
Buffer I/O error on device dm-12, logical block 8
FAT: Unrecognized mount option "nouuid" or missing value
I create snapshot while test2 is busy. (I/O origin volume)
but even I stopped writing data (already got error), sometime it still
happen. 1 out of 3
-bash-3.00# lvs -a
/dev/VG01/test2_4: read failed after 0 of 4096 at 0: Input/output error
/dev/VG01/test2_7: read failed after 0 of 4096 at 0: Input/output error
/dev/VG01/test2_10: read failed after 0 of 4096 at 0: Input/output error
lv1 VG01 -wi-ao 256.00M
lv2 VG01 -wi-ao 1.00G
lv3 VG01 -wi-a- 64.00M
lv4 VG01 -wi-ao 512.00M
lv5 VG01 -wi-ao 128.00M
test2 VG01 owi-ao 29.31G
test2_1 VG01 swi-a- 2.94G test2 38.28
test2_10 VG01 Swi-I- 2.94G test2 100.00
test2_2 VG01 swi-a- 2.94G test2 38.27
test2_3 VG01 swi-a- 2.94G test2 0.01
test2_4 VG01 Swi-I- 2.94G test2 100.00
test2_5 VG01 swi-a- 2.94G test2 0.00
test2_6 VG01 swi-a- 2.94G test2 0.00
test2_7 VG01 Swi-I- 2.94G test2 100.00
test2_8 VG01 swi-a- 2.94G test2 0.00
test2_9 VG01 swi-a- 2.94G test2 0.00
Rocky
[-- Attachment #2: Type: text/html, Size: 7546 bytes --]
next prev parent reply other threads:[~2005-12-15 3:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-14 3:37 [linux-lvm] Invalid new snapshot Lee Rocky
2005-12-14 14:51 ` Alasdair G Kergon
2005-12-15 3:02 ` Lee Rocky [this message]
2005-12-15 6:19 ` Lee Rocky
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=539807300512141902w3cfa6ecdk@mail.gmail.com \
--to=rocky366@gmail.com \
--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).