On Aug 29, 2013, at 7:44 PM, Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx> wrote: > > More information would be helpful, specifically WRT the device stack > underlying mkfs.xfs. I.e. we need to know more about the LVM configuration. > > See: > > http://xfs.org/index.php/XFS_FAQ#Q:_What_information_should_I_include_when_reporting_a_problem.3F Summary: laptop, one HDD, one 402GB partition is made into a PV, one VG is created with that PV and is the only VG on the system, one 400GB logical volume pool is created, one 100GB virtual sized logical volume is created from the thin pool. Linux f19s.local 3.10.9-200.fc19.x86_64 #1 SMP Wed Aug 21 19:27:58 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux xfsprogs-3.1.10-2.fc19.x86_64 lvm2-2.02.98-12.fc19.x86_64 DMI: Apple Inc. MacBookPro4,1/Mac-F42C89C8 WDC WD5000BEVT-22ZAT0 [root@f19s ~]# gdisk -l /dev/sda GPT fdisk (gdisk) version 0.8.7 Partition table scan: MBR: protective BSD: not present APM: not present GPT: present Found valid GPT with protective MBR; using GPT. Disk /dev/sda: 976773168 sectors, 465.8 GiB Logical sector size: 512 bytes Disk identifier (GUID): CB8CACD3-0BDB-46E0-AD6A-D7F99915EA2D Partition table holds up to 128 entries First usable sector is 34, last usable sector is 976773134 Partitions will be aligned on 8-sector boundaries Total free space is 478 sectors (239.0 KiB) Number Start (sector) End (sector) Size Code Name 1 40 409639 200.0 MiB EF00 EFI System Partition 2 409640 49237767 23.3 GiB AF00 Mac 3 49237768 50507303 619.9 MiB AB00 Recovery HD 4 50507776 50712575 100.0 MiB AF00 fedoraEFI 5 50712576 67096575 7.8 GiB 8200 swap 6 67096576 133308415 31.6 GiB 8300 fedoraroot 7 133308416 976773134 402.2 GiB 8E00 LVM2 [root@f19s ~]# pvs PV VG Fmt Attr PSize PFree /dev/sda7 vg1 lvm2 a-- 402.19g 188.00m [root@f19s ~]# lvdisplay --- Logical volume --- LV Name thinp VG Name vg1 LV UUID mKI9dj-1CsO-Ke7e-JcMM-NUDH-MpOD-yMl8Da LV Write Access read/write LV Creation host, time f19s.local, 2013-08-29 00:14:38 -0600 LV Pool transaction ID 1 LV Pool metadata thinp_tmeta LV Pool data thinp_tdata LV Pool chunk size 4.00 MiB LV Zero new blocks yes LV Status available # open 0 LV Size 402.00 GiB Allocated pool data 0.95% Allocated metadata 1.12% Current LE 102912 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:3 --- Logical volume --- LV Path /dev/vg1/data LV Name data VG Name vg1 LV UUID yL0g16-qjUq-20MJ-Fu3I-q5AH-H8ed-LOhNwS LV Write Access read/write LV Creation host, time f19s.local, 2013-08-29 00:15:49 -0600 LV Pool name thinp LV Status available # open 0 LV Size 100.00 GiB Mapped size 3.83% Current LE 25600 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:4 Commands to create the thinp volume: [root@f19s ~]# pvcreate /dev/sda7 Physical volume "/dev/sda7" successfully created [root@f19s ~]# vgcreate vg1 /dev/sda7 Volume group "vg1" successfully created [root@f19s ~]# lvcreate -L 400G --type thin-pool --thinpool thinp vg1 device-mapper: remove ioctl on failed: Device or resource busy Logical volume "thinp" created [root@f19s ~]# lvcreate -V 100G -T vg1/thinp --name data Logical volume "data" created [root@f19s ~]# mkfs.xfs /dev/vg1/data meta-data=/dev/vg1/data isize=256 agcount=16, agsize=1638400 blks = sectsz=512 attr=2, projid32bit=0 data = bsize=4096 blocks=26214400, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0 log =internal log bsize=4096 blocks=12800, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 Whereas if I mkfs.xfs on /dev/sda7, or if I create a regular LV rather than a thinp volume, agcount is 4. It doesn't matter whether I create the thinp with the chunk option set to default (as above) or 1MB or 4MB. Chris Murphy _______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
