From: Killian De Volder <killian.de.volder@megasoft.be>
To: lvm-devel@redhat.com
Subject: pvmove + loop device eats data
Date: Thu, 14 Jun 2012 12:03:48 +0200 [thread overview]
Message-ID: <4FD9B704.7010906@megasoft.be> (raw)
Hello,
Today I needed some space, so I wiped up a disk, threw a file on it, and pmoved it.
Done my resizes, and moved the data back, only to see my data disappear.
(lv was filled with zero's).
The steps required to reproduce the problem are below?
Did I do something wrong, or did I stumble upon a bug ?
Kind regards,
Killian
# lvm version
LVM version: 2.02.88(2) (2011-08-19)
Library version: 1.02.67 (2011-08-19)
Driver version: 4.22.0
# dmsetup version
Library version: 1.02.67 (2011-08-19)
Driver version: 4.22.0
Kernel version: 3.2.1-gentoo-r2
#dd of=test_pv1 if=/dev/zero bs=1M seek=512 count=0
0+0 records in
0+0 records out
0 bytes (0 B) copied, 1,0151e-05 s, 0,0 kB/s
#dd of=test_pv2 if=/dev/zero bs=1M seek=512 count=0
0+0 records in
0+0 records out
0 bytes (0 B) copied, 1,0369e-05 s, 0,0 kB/s
#losetup /dev/loop0 test_pv1
#losetup /dev/loop1 test_pv2
#pvcreate /dev/loop0
File descriptor 6 (pipe:[839]) leaked on pvcreate invocation. Parent PID 14507: bash
File descriptor 8 (pipe:[841]) leaked on pvcreate invocation. Parent PID 14507: bash
Writing physical volume data to disk "/dev/loop0"
#pvcreate /dev/loop1
File descriptor 6 (pipe:[839]) leaked on pvcreate invocation. Parent PID 14507: bash
File descriptor 8 (pipe:[841]) leaked on pvcreate invocation. Parent PID 14507: bash
Writing physical volume data to disk "/dev/loop1"
#vgcreate test /dev/loop0 /dev/loop1
File descriptor 6 (pipe:[839]) leaked on vgcreate invocation. Parent PID 14507: bash
File descriptor 8 (pipe:[841]) leaked on vgcreate invocation. Parent PID 14507: bash
pvs
Volume group "test" successfully created
#lvcreate -L 1M test
File descriptor 6 (pipe:[839]) leaked on lvcreate invocation. Parent PID 14507: bash
File descriptor 8 (pipe:[841]) leaked on lvcreate invocation. Parent PID 14507: bash
Rounding up size to full physical extent 4,00 MiB
Logical volume "lvol0" created
#echo a > /dev/test/lvol0
# cat /dev/test/lvol0
a
# pvmove /dev/loop0 /dev/loop1
File descriptor 6 (pipe:[839]) leaked on pvmove invocation. Parent PID 14507: bash
File descriptor 8 (pipe:[841]) leaked on pvmove invocation. Parent PID 14507: bash
/dev/loop0: Moved: 100,0%
# cat /dev/test/lvol0
#
next reply other threads:[~2012-06-14 10:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-14 10:03 Killian De Volder [this message]
2012-06-15 10:11 ` pvmove + loop device eats data Zdenek Kabelac
2012-06-15 15:54 ` Alasdair G Kergon
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=4FD9B704.7010906@megasoft.be \
--to=killian.de.volder@megasoft.be \
--cc=lvm-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.