http://bugzilla.suse.com/show_bug.cgi?id=1006952
http://bugzilla.suse.com/show_bug.cgi?id=1006952#c10
--- Comment #10 from zhilong liu ---
1. prepare disks
# dd if=/dev/zero of=test1 bs=1M count=1000
1000+0 records in
1000+0 records out
1048576000 bytes (1.0 GB, 1000 MiB) copied, 3.2826 s, 319 MB/s
# cp test1 test2
# losetup /dev/loop2 test1
# losetup /dev/loop2 test2
2. create pvs
# pvcreate /dev/loop1 /dev/loop2
allocation/use_blkid_wiping=1 configuration setting is set while LVM is not
compiled with blkid wiping support.
Falling back to native LVM signature detection.
allocation/use_blkid_wiping=1 configuration setting is set while LVM is not
compiled with blkid wiping support.
Falling back to native LVM signature detection.
Physical volume "/dev/loop1" successfully created.
Physical volume "/dev/loop2" successfully created.
linux-tjrh:~ # vgcreate vg1 /dev/loop1 /dev/loop2
allocation/use_blkid_wiping=1 configuration setting is set while LVM is not
compiled with blkid wiping support.
Falling back to native LVM signature detection.
allocation/use_blkid_wiping=1 configuration setting is set while LVM is not
compiled with blkid wiping support.
Falling back to native LVM signature detection.
Volume group "vg1" successfully created
linux-tjrh:~ # pvs
PV VG Fmt Attr PSize PFree
/dev/loop1 vg1 lvm2 a-- 996.00m 996.00m
/dev/loop2 vg1 lvm2 a-- 996.00m 996.00m
linux-tjrh:~ # vgs
VG #PV #LV #SN Attr VSize VFree
vg1 2 0 0 wz--n- 1.95g 1.95g
linux-tjrh:~ # lvcreate -n CacheDataLV -L 100M vg1 /dev/loop1
allocation/use_blkid_wiping=1 configuration setting is set while LVM is not
compiled with blkid wiping support.
Falling back to native LVM signature detection.
Logical volume "CacheDataLV" created.
linux-tjrh:~ # lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log
Cpy%Sync Convert
CacheDataLV vg1 -wi-a----- 100.00m
linux-tjrh:~ # lvs -o +cache_mode
LV VG Attr LSize Pool Origin Data% Meta% Move Log
Cpy%Sync Convert CacheMode
CacheDataLV vg1 -wi-a----- 100.00m
it's my steps, is it suit for this issue?
-Zhilong
--
You are receiving this mail because:
You are on the CC list for the bug.
bugzilla_noreply＠novell.com