Re: [linux-lvm] Question about filter behavior on pvcreate /dev/md0
Hello Zdenek, Thank you for your reply. Your method works well. I also understand the filter rules gradually. On 6/14/19 4:51 PM, Zdenek Kabelac wrote: > Dne 13. 06. 19 v 9:41 Heming Zhao napsal(a): >> Hello List, >> >> I created a md device, and used pvcreate to format it. >> But the pvcreate was failed with filter rules. >> the filter in /etc/lvm/lvm.conf: >> ``` >> filter = [ "r|/dev/.*/by-path/.*|", "r|/dev/.*/by-id/.*|", >> "r|/dev/fd.*|", "r|/dev/cdrom|" ] >> ``` > > > Hi > > This filter mostly eliminates ANY block device you have in the system. > The logic of filtering can be seen as puzzling, but please try to read > carefully comments in lvm.conf about filtering. It's explained there in > the great detail. > > As soon as the 'accept' rule is seen - the device gets accepted. > Otherwise if you remove device path - all it's associated clones will be > also removed. > > So when you block device generates one of /dev/*/by-path access paths > (and I'd assume /dev/md0 should be) - it gets removed. > > As 'quick fix' you can add 'a' rule for /dev/md.*... > > Regards > > Zdenek > ___ 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/
Re: [linux-lvm] Maximum address used by a virtual disk on a thin pool.
Dne 13. 06. 19 v 21:54 Gionatan Danti napsal(a): Il 13-06-2019 18:05 Ilia Zykov ha scritto: Hello. Tell me please, how can I get the maximum address used by a virtual disk (disk created with -V VirtualSize). I have several large virtual disks, but they use only a small part at the beginning of the disk. For example: # lvs LV VG Attr LSize Pool Origin Data% mylvm CVG Vwi-aot--- 100,00g fastheap 7,13 Please advise me how to determine from which address the virtual disk did not allocate real disk space? And all the data read from addresses greater than this address will be exactly zeros. Or maybe, how can I get map of the used chunks of disk? Thanks. Maybe thin_dump[1] can help you? Regards. [1] https://linux.die.net/man/8/thin_dump Hi There is even better tool that can expose in 'great detail' ownership of individual thin-pool chunks for each thin volume - if that's what you are looking for. See 'man thin_ls' Regards Zdenek ___ 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/
Re: [linux-lvm] Question about filter behavior on pvcreate /dev/md0
Dne 13. 06. 19 v 9:41 Heming Zhao napsal(a): Hello List, I created a md device, and used pvcreate to format it. But the pvcreate was failed with filter rules. the filter in /etc/lvm/lvm.conf: ``` filter = [ "r|/dev/.*/by-path/.*|", "r|/dev/.*/by-id/.*|", "r|/dev/fd.*|", "r|/dev/cdrom|" ] ``` Hi This filter mostly eliminates ANY block device you have in the system. The logic of filtering can be seen as puzzling, but please try to read carefully comments in lvm.conf about filtering. It's explained there in the great detail. As soon as the 'accept' rule is seen - the device gets accepted. Otherwise if you remove device path - all it's associated clones will be also removed. So when you block device generates one of /dev/*/by-path access paths (and I'd assume /dev/md0 should be) - it gets removed. As 'quick fix' you can add 'a' rule for /dev/md.*... Regards Zdenek ___ 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/
