Linux LVM

• Thread Index

• Re: Import duplicate VG from a read-only device
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Import duplicate VG from a read-only device
  • From: Stuart D Gathman <stuart@xxxxxxxxxxx>
• Re: Import duplicate VG from a read-only device
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Import duplicate VG from a read-only device
  • From: Erwin van Londen <erwin@xxxxxxxxxxxxxxxxxx>
• Re: Import duplicate VG from a read-only device
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Import duplicate VG from a read-only device
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: hungtask in dm code raised by concurrent run refresh and remove command
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• hungtask in dm code raised by concurrent run refresh and remove command
  • From: "wangzhiqiang (Q)" <wangzhiqiang95@xxxxxxxxxx>
• Re: lvconvert --type raid5 failure
  • From: Adam Niescierowicz <adam.niescierowicz@xxxxxxxxxx>
• lvconvert --type raid5 failure
  • From: Adam Niescierowicz <adam.niescierowicz@xxxxxxxxxx>
• Re: lvm2/dm-thin snapshot memory and disk overhead
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• lvm2/dm-thin snapshot memory and disk overhead
  • From: Drew Eckhardt <drew.eckhardt2@xxxxxxxxx>
• Re: Help diagnosing lvm ioctl log spam
  • From: Fabricio Winter <admin@xxxxxxxxxx>
• Re: Help diagnosing lvm ioctl log spam
  • From: Erwin van Londen <erwin@xxxxxxxxxxxxxxxxxx>
• Re: Help diagnosing lvm ioctl log spam
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: Help diagnosing lvm ioctl log spam
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Help diagnosing lvm ioctl log spam
  • From: Fabricio Winter <admin@xxxxxxxxxx>
• Unsubscribe
  • From: "box, listen" <listen@xxxxxxxx>
• Re: --autobackup option
  • From: Mike <debian@xxxxxxxxxxxxxxxxxxxxx>
• Re: --autobackup option
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• --autobackup option
  • From: debian@xxxxxxxxxxxxxxxxxxxxx
• Re: Guidance on increasing cache_pool_max_chunks for lvmcache
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Guidance on increasing cache_pool_max_chunks for lvmcache
  • From: Pickles Creator <picklesthecreator@xxxxxxxxx>
• Re: lvm2 deadlock
  • From: Jaco Kroon <jaco@xxxxxxxxx>
• Re: lvm2 deadlock
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: lvm2 deadlock
  • From: Jaco Kroon <jaco@xxxxxxxxx>
• Re: lvm2 deadlock
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: lvm2 deadlock
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: lvm2 deadlock
  • From: Jaco Kroon <jaco@xxxxxxxxx>
• Re: lvm2 deadlock
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: lvm2 deadlock
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re: lvm2 deadlock
  • From: Jaco Kroon <jaco@xxxxxxxxx>
• Re: lvm2 deadlock
  • From: Stuart D Gathman <stuart@xxxxxxxxxxx>
• Re: lvm2 deadlock
  • From: Jaco Kroon <jaco@xxxxxxxxx>
• Re: lvm2 deadlock
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re: lvm2 deadlock
  • From: Jaco Kroon <jaco@xxxxxxxxx>
• Re: lvm2 deadlock
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re: lvm2 deadlock
  • From: Jaco Kroon <jaco@xxxxxxxxx>
• Re: lvm2 deadlock
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: lvm2 deadlock
  • From: Jaco Kroon <jaco@xxxxxxxxx>
• Re: lvm2 deadlock
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• lvm2 deadlock
  • From: Jaco Kroon <jaco@xxxxxxxxx>
• Re: Repeated lvcreate&lvremove quickly increases page cache size
  • From: Ryotaro Banno (伴野 良太郎) <rbanno@xxxxxxxxxxxx>
• Re: Repeated lvcreate&lvremove quickly increases page cache size
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: Repeated lvcreate&lvremove quickly increases page cache size
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Repeated lvcreate&lvremove quickly increases page cache size
  • From: Ryotaro Banno (伴野 良太郎) <rbanno@xxxxxxxxxxxx>
• Re: [PATCH v2 0/7] device mapper udev rules rework
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• Re: [PATCH v2 0/7] device mapper udev rules rework
  • From: Peter Rajnoha <prajnoha@xxxxxxxxxx>
• [PATCH v2 7/7] 10-dm.rules: bump DM_UDEV_RULES_VSN to 3
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• [PATCH v2 6/7] dm udev rules: don't export and save DM_NOSCAN
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• [PATCH v2 5/7] dm udev rules: don't export and save DM_SUSPENDED
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• [PATCH v2 4/7] 11-dm-lvm.rules: don't restore DM_UDEV_DISABLE_OTHER_RULES_FLAG from db
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• [PATCH v2 3/7] 10-dm-rules: don't restore DM_UDEV_DISABLE_OTHER_RULES_FLAG from db
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• [PATCH v2 2/7] 10-dm.rules: test DISK_RO after importing properties
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• [PATCH v2 1/7] 13-dm-disk.rules: import ID_FS_TYPE
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• [PATCH v2 0/7] device mapper udev rules rework
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• Re: [RFC PATCH 5/7] dm udev rules: don't export and save DM_SUSPENDED
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [RFC PATCH 5/7] dm udev rules: don't export and save DM_SUSPENDED
  • From: Peter Rajnoha <prajnoha@xxxxxxxxxx>
• Re: [RFC PATCH 7/7] 10-dm.rules: bump DM_UDEV_RULES_VSN to 3
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [RFC PATCH 5/7] dm udev rules: don't export and save DM_SUSPENDED
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [RFC PATCH 7/7] 10-dm.rules: bump DM_UDEV_RULES_VSN to 3
  • From: Peter Rajnoha <prajnoha@xxxxxxxxxx>
• Re: [RFC PATCH 5/7] dm udev rules: don't export and save DM_SUSPENDED
  • From: Peter Rajnoha <prajnoha@xxxxxxxxxx>
• Re: [RFC PATCH 2/7] 10-dm.rules: don't deactivate devices for DISK_RO=1
  • From: Peter Rajnoha <prajnoha@xxxxxxxxxx>
• Re: [RFC PATCH 7/7] 10-dm.rules: bump DM_UDEV_RULES_VSN to 3
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [RFC PATCH 5/7] dm udev rules: don't export and save DM_SUSPENDED
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [RFC PATCH 2/7] 10-dm.rules: don't deactivate devices for DISK_RO=1
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [RFC PATCH 1/7] 13-dm-disk.rules: import ID_FS_TYPE
  • From: Peter Rajnoha <prajnoha@xxxxxxxxxx>
• Re: [RFC PATCH 2/7] 10-dm.rules: don't deactivate devices for DISK_RO=1
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [RFC PATCH 1/7] 13-dm-disk.rules: import ID_FS_TYPE
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [RFC PATCH 2/7] 10-dm.rules: don't deactivate devices for DISK_RO=1
  • From: Peter Rajnoha <prajnoha@xxxxxxxxxx>
• Re: [RFC PATCH 2/7] 10-dm.rules: don't deactivate devices for DISK_RO=1
  • From: Peter Rajnoha <prajnoha@xxxxxxxxxx>
• Re: [RFC PATCH 7/7] 10-dm.rules: bump DM_UDEV_RULES_VSN to 3
  • From: Peter Rajnoha <prajnoha@xxxxxxxxxx>
• Re: [RFC PATCH 6/7] dm udev rules: don't export and save DM_NOSCAN
  • From: Peter Rajnoha <prajnoha@xxxxxxxxxx>
• Re: [RFC PATCH 5/7] dm udev rules: don't export and save DM_SUSPENDED
  • From: Peter Rajnoha <prajnoha@xxxxxxxxxx>
• Re: [RFC PATCH 4/7] 11-dm-lvm.rules: don't restore DM_UDEV_DISABLE_OTHER_RULES_FLAG from db
  • From: Peter Rajnoha <prajnoha@xxxxxxxxxx>
• Re: [RFC PATCH 3/7] 10-dm-rules: don't restore DM_UDEV_DISABLE_OTHER_RULES_FLAG from db
  • From: Peter Rajnoha <prajnoha@xxxxxxxxxx>
• Re: [RFC PATCH 2/7] 10-dm.rules: don't deactivate devices for DISK_RO=1
  • From: Peter Rajnoha <prajnoha@xxxxxxxxxx>
• Re: [RFC PATCH 1/7] 13-dm-disk.rules: import ID_FS_TYPE
  • From: Peter Rajnoha <prajnoha@xxxxxxxxxx>
• [RFC PATCH 7/7] 10-dm.rules: bump DM_UDEV_RULES_VSN to 3
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• [RFC PATCH 6/7] dm udev rules: don't export and save DM_NOSCAN
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• [RFC PATCH 4/7] 11-dm-lvm.rules: don't restore DM_UDEV_DISABLE_OTHER_RULES_FLAG from db
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• [RFC PATCH 5/7] dm udev rules: don't export and save DM_SUSPENDED
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• [RFC PATCH 3/7] 10-dm-rules: don't restore DM_UDEV_DISABLE_OTHER_RULES_FLAG from db
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• [RFC PATCH 2/7] 10-dm.rules: don't deactivate devices for DISK_RO=1
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• [RFC PATCH 1/7] 13-dm-disk.rules: import ID_FS_TYPE
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• [RFC PATCH 0/7] device mapper udev rules rework
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• Re: error while submitting device barriers: BTRFS+LVM read-only on newer kernels
  • From: Patrick Plenefisch <simonpatp@xxxxxxxxx>
• error while submitting device barriers: BTRFS+LVM read-only on newer kernels
  • From: Patrick Plenefisch <simonpatp@xxxxxxxxx>
• Re: About DM_UDEV_DISABLE_OTHER_RULES_FLAG and DM_NOSCAN
  • From: Peter Rajnoha <prajnoha@xxxxxxxxxx>
• Re: About DM_UDEV_DISABLE_OTHER_RULES_FLAG and DM_NOSCAN
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• Re: About DM_UDEV_DISABLE_OTHER_RULES_FLAG and DM_NOSCAN
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• Re: [PATCH v3] 11-dm-mpath.rules: handle reloads during coldplug events
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• [PATCH v3 6/6] 11-dm-mpath.rules: Don't force activation while device is suspended
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• [PATCH v3 5/6] 11-dm-mpath.rules: clear DM_DISABLE_OTHER_RULES_FLAG for coldplug events
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• [PATCH v3 4/6] 11-dm-mpath.rules: don't save DM_UDEV_DISABLE_OTHER_RULES_FLAG_OLD
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• [PATCH v3 3/6] 11-dm-mpath.rules: handle reloads during coldplug events
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• [PATCH v3 2/6] 11-dm-mpath.rules: don't import DM_UDEV_DISABLE_OTHER_RULES_FLAG
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• [PATCH v3 0/6] udev rule and CI improvements
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• [PATCH v3 1/6] 11-dm-mpath.rules: use import logic like 13-dm-disk.rules
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• Re: [PATCH v2 6/7] 11-dm-mpath.rules: Don't force activation while device is suspended
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• Re: About DM_UDEV_DISABLE_OTHER_RULES_FLAG and DM_NOSCAN
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• Re: About DM_UDEV_DISABLE_OTHER_RULES_FLAG and DM_NOSCAN
  • From: Peter Rajnoha <prajnoha@xxxxxxxxxx>
• Re: About DM_UDEV_DISABLE_OTHER_RULES_FLAG and DM_NOSCAN
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• Re: About DM_UDEV_DISABLE_OTHER_RULES_FLAG and DM_NOSCAN
  • From: Peter Rajnoha <prajnoha@xxxxxxxxxx>
• [PATCH v3] 11-dm-mpath.rules: handle reloads during coldplug events
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• Re: [PATCH v2 4/7] 11-dm-mpath.rules: don't save DM_UDEV_DISABLE_OTHER_RULES_FLAG_OLD
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• Re: [PATCH v2 7/7] multipath-tools: Makefile.inc: set _FILE_OFFSET_BITS=64
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• Re: [PATCH v2 6/7] 11-dm-mpath.rules: Don't force activation while device is suspended
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• Re: [PATCH v2 5/7] 11-dm-mpath.rules: clear DM_DISABLE_OTHER_RULES_FLAG for coldplug events
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• Re: [PATCH v2 4/7] 11-dm-mpath.rules: don't save DM_UDEV_DISABLE_OTHER_RULES_FLAG_OLD
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• Re: [PATCH v2 3/7] 11-dm-mpath.rules: handle reloads during coldplug events
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• Re: [PATCH v2 2/7] 11-dm-mpath.rules: don't import DM_UDEV_DISABLE_OTHER_RULES_FLAG
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• [PATCH v2 7/7] multipath-tools: Makefile.inc: set _FILE_OFFSET_BITS=64
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• [PATCH v2 6/7] 11-dm-mpath.rules: Don't force activation while device is suspended
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• [PATCH v2 5/7] 11-dm-mpath.rules: clear DM_DISABLE_OTHER_RULES_FLAG for coldplug events
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• [PATCH v2 4/7] 11-dm-mpath.rules: don't save DM_UDEV_DISABLE_OTHER_RULES_FLAG_OLD
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• [PATCH v2 3/7] 11-dm-mpath.rules: handle reloads during coldplug events
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• [PATCH v2 2/7] 11-dm-mpath.rules: don't import DM_UDEV_DISABLE_OTHER_RULES_FLAG
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• [PATCH v2 1/7] 11-dm-mpath.rules: use import logic like 13-dm-disk.rules
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• [PATCH v2 0/7] udev rule and CI improvements
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• About DM_UDEV_DISABLE_OTHER_RULES_FLAG and DM_NOSCAN
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• Re: [PATCH 3/6] 11-dm-mpath.rules: handle reloads during coldplug events
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• Re: [PATCH 2/6] 11-dm-mpath.rules: don't import properties that are already set
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• Re: [PATCH 2/6] 11-dm-mpath.rules: don't import properties that are already set
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• Re: [PATCH 4/6] 11-dm-mpath.rules: don't save DM_UDEV_DISABLE_OTHER_RULES_FLAG_OLD
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• Re: [PATCH 1/6] 11-dm-mpath.rules: use import logic like 13-dm-disk.rules
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• [PATCH 6/6] multipath-tools: Makefile.inc: set _FILE_OFFSET_BITS=64
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• [PATCH 5/6] 11-dm-mpath.rules: clear DM_DISABLE_OTHER_RULES_FLAG for coldplug events
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• [PATCH 3/6] 11-dm-mpath.rules: handle reloads during coldplug events
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• [PATCH 4/6] 11-dm-mpath.rules: don't save DM_UDEV_DISABLE_OTHER_RULES_FLAG_OLD
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• [PATCH 1/6] 11-dm-mpath.rules: use import logic like 13-dm-disk.rules
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• [PATCH 2/6] 11-dm-mpath.rules: don't import properties that are already set
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• [PATCH 0/6] udev rule and CI improvements
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• Re: [PATCH 4/6] 11-dm-mpath.rules: handle reloads during coldplug events
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• Re: [PATCH 4/6] 11-dm-mpath.rules: handle reloads during coldplug events
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• Re: [PATCH 4/6] 11-dm-mpath.rules: handle reloads during coldplug events
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• Re: [PATCH 3/6] 11-dm-mpath.rules: use import logic like 13-dm-disk.rules
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• Re: [PATCH 1/6] 11-dm-mpath.rules: don't import properties that are already set
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• Re: [PATCH 6/6] multipathd: don't activate socket activation by default
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• Re: [PATCH 5/6] multipath: udev rules: use configured $(bindir) in udev rules
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• Re: [PATCH 4/6] 11-dm-mpath.rules: handle reloads during coldplug events
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• Re: [PATCH 3/6] 11-dm-mpath.rules: use import logic like 13-dm-disk.rules
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• Re: [PATCH 2/6] 11-dm-mpath.rules: fix list of imported properties
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• Re: [PATCH 1/6] 11-dm-mpath.rules: don't import properties that are already set
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• Re: [PATCH 1/6] 11-dm-mpath.rules: don't import properties that are already set
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• Re: [PATCH 1/6] 11-dm-mpath.rules: don't import properties that are already set
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• [PATCH 6/6] multipathd: don't activate socket activation by default
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• [PATCH 5/6] multipath: udev rules: use configured $(bindir) in udev rules
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• [PATCH 4/6] 11-dm-mpath.rules: handle reloads during coldplug events
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• [PATCH 3/6] 11-dm-mpath.rules: use import logic like 13-dm-disk.rules
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• [PATCH 0/6] multipath-tools: udev rules and service improvements
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• [PATCH 2/6] 11-dm-mpath.rules: fix list of imported properties
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• [PATCH 1/6] 11-dm-mpath.rules: don't import properties that are already set
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• Re: Any way in LVM to deal with 512e vs 4Kn physical devices?
  • From: Demi Marie Obenour <demi@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Any way in LVM to deal with 512e vs 4Kn physical devices?
  • From: Glenn Washburn <development@xxxxxxxxxxxxxxx>
• Re: Any way in LVM to deal with 512e vs 4Kn physical devices?
  • From: Phillip Susi <phill@xxxxxxxxxxxx>
• Re: [Question] why not flush device cache at _vg_commit_raw
  • From: Heming Zhao <heming.zhao@xxxxxxxx>
• Re: Any way in LVM to deal with 512e vs 4Kn physical devices?
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re: Any way in LVM to deal with 512e vs 4Kn physical devices?
  • From: Phillip Susi <phill@xxxxxxxxxxxx>
• Re: [Question] why not flush device cache at _vg_commit_raw
  • From: Anthony Iliopoulos <ailiop@xxxxxxxx>
• Re: [Question] why not flush device cache at _vg_commit_raw
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: [Question] why not flush device cache at _vg_commit_raw
  • From: Anthony Iliopoulos <ailiop@xxxxxxxx>
• Re: [Question] why not flush device cache at _vg_commit_raw
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: [Question] why not flush device cache at _vg_commit_raw
  • From: Demi Marie Obenour <demi@xxxxxxxxxxxxxxxxxxxxxx>
• Re: [Question] why not flush device cache at _vg_commit_raw
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• Re: [Question] why not flush device cache at _vg_commit_raw
  • From: Su Yue <glass.su@xxxxxxxx>
• Re: [Question] why not flush device cache at _vg_commit_raw
  • From: Anthony Iliopoulos <ailiop@xxxxxxxx>
• Re: [Question] why not flush device cache at _vg_commit_raw
  • From: Ilia Zykov <mail@xxxxxxxxxxx>
• Re: [Question] why not flush device cache at _vg_commit_raw
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: [Question] why not flush device cache at _vg_commit_raw
  • From: Anthony Iliopoulos <ailiop@xxxxxxxx>
• Re: [Question] why not flush device cache at _vg_commit_raw
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• [Question] why not flush device cache at _vg_commit_raw
  • From: Su Yue <glass.su@xxxxxxxx>
• Re: add volatile flag to PV/LVs (for cache) to avoid degraded state on reboot
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: Any way in LVM to deal with 512e vs 4Kn physical devices?
  • From: Andy Smith <andy@xxxxxxxxxxxxxx>
• Re: add volatile flag to PV/LVs (for cache) to avoid degraded state on reboot
  • From: lists.linux.dev@xxxxxxxxx
• Re: Any way in LVM to deal with 512e vs 4Kn physical devices?
  • From: Phillip Susi <phill@xxxxxxxxxxxx>
• Re: Any way in LVM to deal with 512e vs 4Kn physical devices?
  • From: Andy Smith <andy@xxxxxxxxxxxxxx>
• Re: add volatile flag to PV/LVs (for cache) to avoid degraded state on reboot
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: add volatile flag to PV/LVs (for cache) to avoid degraded state on reboot
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: add volatile flag to PV/LVs (for cache) to avoid degraded state on reboot
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Any way in LVM to deal with 512e vs 4Kn physical devices?
  • From: Ilia Zykov <mail@xxxxxxxxxxx>
• Re: Any way in LVM to deal with 512e vs 4Kn physical devices?
  • From: Phillip Susi <phill@xxxxxxxxxxxx>
• Re: Any way in LVM to deal with 512e vs 4Kn physical devices?
  • From: Phillip Susi <phill@xxxxxxxxxxxx>
• Re: Any way in LVM to deal with 512e vs 4Kn physical devices?
  • From: Phillip Susi <phill@xxxxxxxxxxxx>
• Re: Any way in LVM to deal with 512e vs 4Kn physical devices?
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re: Any way in LVM to deal with 512e vs 4Kn physical devices?
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: Any way in LVM to deal with 512e vs 4Kn physical devices?
  • From: Andy Smith <andy@xxxxxxxxxxxxxx>
• Re: add volatile flag to PV/LVs (for cache) to avoid degraded state on reboot
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: Any way in LVM to deal with 512e vs 4Kn physical devices?
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: Any way in LVM to deal with 512e vs 4Kn physical devices?
  • From: Andy Smith <andy@xxxxxxxxxxxxxx>
• Re: Any way in LVM to deal with 512e vs 4Kn physical devices?
  • From: Andy Smith <andy@xxxxxxxxxxxxxx>
• Re: Any way in LVM to deal with 512e vs 4Kn physical devices?
  • From: Andy Smith <andy@xxxxxxxxxxxxxx>
• Re: Any way in LVM to deal with 512e vs 4Kn physical devices?
  • From: Ilia Zykov <mail@xxxxxxxxxxx>
• Re: Any way in LVM to deal with 512e vs 4Kn physical devices?
  • From: Phillip Susi <phill@xxxxxxxxxxxx>
• Re: Any way in LVM to deal with 512e vs 4Kn physical devices?
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Any way in LVM to deal with 512e vs 4Kn physical devices?
  • From: Andy Smith <andy@xxxxxxxxxxxxxx>
• pvmove stuck/hung
  • From: Devin Vance <devin@xxxxxxxxxx>
• add volatile flag to PV/LVs (for cache) to avoid degraded state on reboot
  • From: lists.linux.dev@xxxxxxxxx
• pvmove stuck/hung
  • From: Devin Vance <devin@xxxxxxxxxx>
• Re: Unable to resize a logical volume due to wrong reported asked size
  • From: François-Xavier Payet <fx@xxxxxxxx>
• Re: Unable to resize a logical volume due to wrong reported asked size
  • From: David Teigland <teigland@xxxxxxxxxx>
• Unable to resize a logical volume due to wrong reported asked size
  • From: François-Xavier Payet <fx@xxxxxxxx>
• Re: Should issue_discards be enabled when e2scrub is used on an SSD?
  • From: Mikhail Morfikov <mmorfikov@xxxxxxxxx>
• Re: Should issue_discards be enabled when e2scrub is used on an SSD?
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: Should issue_discards be enabled when e2scrub is used on an SSD?
  • From: Mikhail Morfikov <mmorfikov@xxxxxxxxx>
• Re: Should issue_discards be enabled when e2scrub is used on an SSD?
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Should issue_discards be enabled when e2scrub is used on an SSD?
  • From: Mikhail Morfikov <mmorfikov@xxxxxxxxx>
• Re: lvmcache not promoting blocks when there's free RAM
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• lvm2 2.03.23 git tag
  • From: Christian Hesse <list@xxxxxxxx>
• Re: lvmcache not promoting blocks when there's free RAM
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: lvmcache not promoting blocks when there's free RAM
  • From: Roberto Fastec <roberto.fastec@xxxxxxxxx>
• lvmcache not promoting blocks when there's free RAM
  • From: Wolf480pl <wolf480@xxxxxxxxxx>
• Re: vgcreate fails with 'already exists in filesystem' error
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• vgcreate fails with 'already exists in filesystem' error
  • From: divya mohan <m.divya.mohan@xxxxxxxx>
• [PATCH] man: add inte(g)rity to man lvs
  • From: Lukas Herbolt <lukas@xxxxxxxxxxx>
• Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
  • From: Demi Marie Obenour <demi@xxxxxxxxxxxxxxxxxxxxxx>
• Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
  • From: Demi Marie Obenour <demi@xxxxxxxxxxxxxxxxxxxxxx>
• Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
  • From: Demi Marie Obenour <demi@xxxxxxxxxxxxxxxxxxxxxx>
• Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
  • From: Heming Zhao <heming.zhao@xxxxxxxx>
• Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
  • From: Peter Rajnoha <prajnoha@xxxxxxxxxx>
• Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
  • From: Heming Zhao <heming.zhao@xxxxxxxx>
• Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
  • From: Heming Zhao <heming.zhao@xxxxxxxx>
• Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
  • From: Peter Rajnoha <prajnoha@xxxxxxxxxx>
• Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
  • From: Peter Rajnoha <prajnoha@xxxxxxxxxx>
• Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
  • From: Heming Zhao <heming.zhao@xxxxxxxx>
• Re: Problems on enabling snapshots after reboot,.
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Problems on enabling snapshots after reboot,.
  • From: Borut Rozman <borut.rozman@xxxxxxxxxxxxxx>
• linux-lvm has migrated to lists.linux.dev [was: Re: Welcome to the "linux-lvm" mailing list]
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: Is MD array (containing a PV) reducible?
  • From: Phillip Susi <phill@xxxxxxxxxxxx>
• Re: Is MD array (containing a PV) reducible?
  • From: "Brian J. Murrell" <brian@xxxxxxxxxxxxxxx>
• Re: Is MD array (containing a PV) reducible?
  • From: Phillip Susi <phill@xxxxxxxxxxxx>
• Re: Is MD array (containing a PV) reducible?
  • From: "Brian J. Murrell" <brian@xxxxxxxxxxxxxxx>
• Re: Is MD array (containing a PV) reducible?
  • From: Phillip Susi <phill@xxxxxxxxxxxx>
• Re: Is MD array (containing a PV) reducible?
  • From: "Brian J. Murrell" <brian@xxxxxxxxxxxxxxx>
• Re: Is MD array (containing a PV) reducible?
  • From: Phillip Susi <phill@xxxxxxxxxxxx>
• Re: Is MD array (containing a PV) reducible?
  • From: grumpy@xxxxxxxxxxxxx
• Re: Is MD array (containing a PV) reducible?
  • From: "Brian J. Murrell" <brian@xxxxxxxxxxxxxxx>
• Re: Is MD array (containing a PV) reducible?
  • From: Phillip Susi <phill@xxxxxxxxxxxx>
• Is MD array (containing a PV) reducible?
  • From: "Brian J. Murrell" <brian@xxxxxxxxxxxxxxx>
• How to flush dirty cache with dm-cache?
  • From: Forza <forza@xxxxxxxxxxxx>
• Re: Can I combine LUKS and LVM to achieve encryption and snapshots?
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: Can I combine LUKS and LVM to achieve encryption and snapshots?
  • From: Roberto Fastec <roberto.fastec@xxxxxxxxx>
• Re: Can I combine LUKS and LVM to achieve encryption and snapshots?
  • From: Jean-Marc Saffroy <saffroy+redhat@xxxxxxxxx>
• Re: Can I combine LUKS and LVM to achieve encryption and snapshots?
  • From: Jean-Marc Saffroy <saffroy+redhat@xxxxxxxxx>
• Re: Can I combine LUKS and LVM to achieve encryption and snapshots?
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: Can I combine LUKS and LVM to achieve encryption and snapshots?
  • From: Jean-Marc Saffroy <saffroy+redhat@xxxxxxxxx>
• Re: Can I combine LUKS and LVM to achieve encryption and snapshots?
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: Can I combine LUKS and LVM to achieve encryption and snapshots?
  • From: Harald Dunkel <harald.dunkel@xxxxxxxxxx>
• Re: Can I combine LUKS and LVM to achieve encryption and snapshots?
  • From: Demi Marie Obenour <demi@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Can I combine LUKS and LVM to achieve encryption and snapshots?
  • From: Stuart D Gathman <stuart@xxxxxxxxxxx>
• Re: Can I combine LUKS and LVM to achieve encryption and snapshots?
  • From: Jean-Marc Saffroy <saffroy+redhat@xxxxxxxxx>
• Re: Can I combine LUKS and LVM to achieve encryption and snapshots?
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Can I combine LUKS and LVM to achieve encryption and snapshots?
  • From: Jean-Marc Saffroy <saffroy+redhat@xxxxxxxxx>
• Re: Trouble Booting Custom Kernel with QEMU: dracut-initqueue timeout waiting for /dev/sysvg/root
  • From: Vishal Chourasia <vishalc@xxxxxxxxxxxxx>
• Re: Swapping LLVM drive
  • From: Phillip Susi <phill@xxxxxxxxxxxx>
• Re: Trouble Booting Custom Kernel with QEMU: dracut-initqueue timeout waiting for /dev/sysvg/root
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: Trouble Booting Custom Kernel with QEMU: dracut-initqueue timeout waiting for /dev/sysvg/root
  • From: Vishal Chourasia <vishalc@xxxxxxxxxxxxx>
• Re: Trouble Booting Custom Kernel with QEMU: dracut-initqueue timeout waiting for /dev/sysvg/root
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Trouble Booting Custom Kernel with QEMU: dracut-initqueue timeout waiting for /dev/sysvg/root
  • From: Vishal Chourasia <vishalc@xxxxxxxxxxxxx>
• Re: vgchange acquire an exclusive VG lock for refresh
  • From: "wangzhiqiang (Q)" <wangzhiqiang95@xxxxxxxxxx>
• Re: vgchange acquire an exclusive VG lock for refresh
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: Swapping LLVM drive
  • From: Stuart D Gathman <stuart@xxxxxxxxxxx>
• Re: Swapping LLVM drive
  • From: Stuart D Gathman <stuart@xxxxxxxxxxx>
• Re: Swapping LLVM drive
  • From: Roska Postit <roskapostit99999@xxxxxxxxx>
• Re: Swapping LLVM drive
  • From: Roska Postit <roskapostit99999@xxxxxxxxx>
• Re: vgchange acquire an exclusive VG lock for refresh
  • From: "wangzhiqiang (Q)" <wangzhiqiang95@xxxxxxxxxx>
• vgchange acquire an exclusive VG lock for refresh
  • From: "wangzhiqiang (Q)" <wangzhiqiang95@xxxxxxxxxx>
• Re: Swapping LLVM drive
  • From: Phillip Susi <phill@xxxxxxxxxxxx>
• Re: Swapping LLVM drive
  • From: Stuart D Gathman <stuart@xxxxxxxxxxx>
• Re: indistinguishable column names ( BA Start Start Start Start )
  • From: matthew patton <pattonme@xxxxxxxxx>
• Swapping LLVM drive
  • From: Roska Postit <roskapostit99999@xxxxxxxxx>
• Re: indistinguishable column names ( BA Start Start Start Start )
  • From: Roland <devzero@xxxxxx>
• Re: indistinguishable column names ( BA Start Start Start Start )
  • From: Marian Csontos <mcsontos@xxxxxxxxxx>
• Re: indistinguishable column names ( BA Start Start Start Start )
  • From: Roland <devzero@xxxxxx>
• Re: indistinguishable column names ( BA Start Start Start Start )
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: indistinguishable column names ( BA Start Start Start Start )
  • From: Roland <devzero@xxxxxx>
• indistinguishable column names ( BA Start Start Start Start )
  • From: Roland <devzero@xxxxxx>
• Re: Problems encountered in compiling lvm packages using the musl Toolchain
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Problems encountered in compiling lvm packages using the musl Toolchain
  • From: 程智星 <zhixing@xxxxxxxxxxxxxx>
• Re: ThinPool performance problem with NVMe
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: ThinPool performance problem with NVMe
  • From: ComputerAdvancedTechnologySYSTEM <hofman.catsystem@xxxxxxxxxxxxxx>
• 答复: The logical volume cannot be activated
  • From: "wangzhiqiang (Q)" <wangzhiqiang95@xxxxxxxxxx>
• Re: Documentation about allowing >2 disk failures?
  • From: Roberto Fastec <roberto.fastec@xxxxxxxxx>
• Re: ThinPool performance problem with NVMe
  • From: matthew patton <pattonme@xxxxxxxxx>
• Re: The logical volume cannot be activated
  • From: David Teigland <teigland@xxxxxxxxxx>
• The logical volume cannot be activated
  • From: "wangzhiqiang (Q)" <wangzhiqiang95@xxxxxxxxxx>
• Documentation about allowing >2 disk failures?
  • From: "Tim 'mithro' Ansell" <me@xxxxxxx>
• ThinPool performance problem with NVMe
  • From: Anton Kulshenko <shallriseagain@xxxxxxxxx>
• Re: lvm2-testsuite stability
  • From: Scott Moser <smoser@xxxxxxxxxxxx>
• Re: lvm2-testsuite stability
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: lvm2-testsuite stability
  • From: Scott Moser <smoser@xxxxxxxxxxxx>
• Re: lvm2-testsuite stability
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• lvm2-testsuite stability
  • From: Scott Moser <ssmoser@xxxxxxxxx>
• lvm2-testsuite stability
  • From: Scott Moser <smoser@xxxxxxxxxxxx>
• Re: Question on RAID integrity limitations
  • From: Cyclic Group Z_1 <cyclicgroup-z1@xxxxxxxxx>
• Re: Question on RAID integrity limitations
  • From: David Teigland <teigland@xxxxxxxxxx>
• Question on RAID integrity limitations
  • From: Cyclic Group Z_1 <cyclicgroup-z1@xxxxxxxxx>
• intermittent transaction ID mismatch with rapid use of thin snapshots
  • From: Michael McCracken <michael.mccracken@xxxxxxxxx>
• Re: badblocks
  • From: Roberto Fastec <roberto.fastec@xxxxxxxxx>
• Re: badblocks
  • From: graeme vetterlein <graeme.lvm@xxxxxxxxxxxxxx>
• Re: badblocks
  • From: Phillip Susi <phill@xxxxxxxxxxxx>
• Re: badblocks
  • From: Phillip Susi <phill@xxxxxxxxxxxx>
• badblocks
  • From: graeme vetterlein <graeme.lvm@xxxxxxxxxxxxxx>
• Re: How to convert a single path to a multipath after using dm-multipath
  • From: Zhiyong Ye <yezhiyong@xxxxxxxxxxxxx>
• Re: How to convert a single path to a multipath after using dm-multipath
  • From: Giorgio Bersano <giorgio.bersano@xxxxxxxxx>
• Re: How to convert a single path to a multipath after using dm-multipath
  • From: Zhiyong Ye <yezhiyong@xxxxxxxxxxxxx>
• Re: How to convert a single path to a multipath after using dm-multipath
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: bug? shrink lv by specifying pv extent to be removed does not behave as expected
  • From: Roberto Fastec <roberto.fastec@xxxxxxxxx>
• Re: bug? shrink lv by specifying pv extent to be removed does not behave as expected
  • From: Roberto Fastec <roberto.fastec@xxxxxxxxx>
• Re: bug? shrink lv by specifying pv extent to be removed does not behave as expected
  • From: Roberto Fastec <roberto.fastec@xxxxxxxxx>
• Re: bug? shrink lv by specifying pv extent to be removed does not behave as expected
  • From: Roberto Fastec <roberto.fastec@xxxxxxxxx>
• Re: How to convert a single path to a multipath after using dm-multipath
  • From: Zhiyong Ye <yezhiyong@xxxxxxxxxxxxx>
• Re: bug? shrink lv by specifying pv extent to be removed does not behave as expected
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: bug? shrink lv by specifying pv extent to be removed does not behave as expected
  • From: Roland <devzero@xxxxxx>
• Re: bug? shrink lv by specifying pv extent to be removed does not behave as expected
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: bug? shrink lv by specifying pv extent to be removed does not behave as expected
  • From: Roland <devzero@xxxxxx>
• Re: bug? shrink lv by specifying pv extent to be removed does not behave as expected
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re: How to convert a single path to a multipath after using dm-multipath
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: is lvmraid 1 thinpool with integrity safe?
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: is lvmraid 1 thinpool with integrity safe?
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• is lvmraid 1 thinpool with integrity safe?
  • From: Arvid Picciani <aep@xxxxxxxx>
• Re: bug? shrink lv by specifying pv extent to be removed does not behave as expected
  • From: matthew patton <pattonme@xxxxxxxxx>
• How to convert a single path to a multipath after using dm-multipath
  • From: Zhiyong Ye <yezhiyong@xxxxxxxxxxxxx>
• Re: bug? shrink lv by specifying pv extent to be removed does not behave as expected
  • From: Stuart D Gathman <stuart@xxxxxxxxxxx>
• Re: bug? shrink lv by specifying pv extent to be removed does not behave as expected
  • From: Roland <devzero@xxxxxx>
• Re: bug? shrink lv by specifying pv extent to be removed does not behave as expected
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re: bug? shrink lv by specifying pv extent to be removed does not behave as expected
  • From: Roland <devzero@xxxxxx>
• Re: bug? shrink lv by specifying pv extent to be removed does not behave as expected
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• bug? shrink lv by specifying pv extent to be removed does not behave as expected
  • From: Roland <devzero@xxxxxx>
• Re: bad checksum in superblock, wanted
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• bad checksum in superblock, wanted
  • From: Delarians <alexsifm@xxxxxxxxx>
• Re: LVM and RO device/partition(s
  • From: lacsaP Patatetom <patatetom@xxxxxxxxx>
• Re: LVM and RO device/partition(s
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: LVM and RO device/partition(s)
  • From: lacsaP Patatetom <patatetom@xxxxxxxxx>
• Re: LVM and RO device/partition(s)
  • From: lacsaP Patatetom <patatetom@xxxxxxxxx>
• Re: LVM and RO device/partition(s)
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• LVM and RO device/partition(s)
  • From: Pascal <patatetom@xxxxxxxxx>
• Re: How to handle Bad Block relocation with LVM?
  • From: Roland <devzero@xxxxxx>
• Re: lvconvert --uncache takes hours
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: lvconvert --uncache takes hours
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re: lvconvert --uncache takes hours
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: lvconvert --uncache takes hours
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re: lvconvert --uncache takes hours
  • From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
• Re: lvconvert --uncache takes hours
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re: lvconvert --uncache takes hours
  • From: Demi Marie Obenour <demi@xxxxxxxxxxxxxxxxxxxxxx>
• lvconvert --uncache takes hours
  • From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
• pvshrink - defrag pv / move extents to the beginning
  • From: Roland <devzero@xxxxxx>
• Re: [External] Re: The feasibility of implementing an alternative snapshot approach
  • From: Zhiyong Ye <yezhiyong@xxxxxxxxxxxxx>
• Re: The feasibility of implementing an alternative snapshot approach
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: The feasibility of implementing an alternative snapshot approach
  • From: Zhiyong Ye <yezhiyong@xxxxxxxxxxxxx>
• Re: The feasibility of implementing an alternative snapshot approach
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: The feasibility of implementing an alternative snapshot approach
  • From: Zhiyong Ye <yezhiyong@xxxxxxxxxxxxx>
• Re: Trouble with balancing physical volumes with pvmove
  • From: John Stoffel <john@xxxxxxxxxxx>
• Re: The feasibility of implementing an alternative snapshot approach
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• The feasibility of implementing an alternative snapshot approach
  • From: Zhiyong Ye <yezhiyong@xxxxxxxxxxxxx>
• Trouble with balancing physical volumes with pvmove
  • From: Robert Osowiecki <robert.osowiecki@xxxxxxxxx>
• Re: lvm-vdo, snapshots and cache
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: lvm-vdo, snapshots and cache
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: lvm-vdo, snapshots and cache
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: lvm-vdo, snapshots and cache
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: lvm-vdo, snapshots and cache
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• lvm-vdo, snapshots and cache
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: How to implement live migration of VMs in thinlv after using lvmlockd
  • From: Zhiyong Ye <yezhiyong@xxxxxxxxxxxxx>
• Re: How to implement live migration of VMs in thinlv after using lvmlockd
  • From: Zhiyong Ye <yezhiyong@xxxxxxxxxxxxx>
• Re: How to implement live migration of VMs in thinlv after using lvmlockd
  • From: Zhiyong Ye <yezhiyong@xxxxxxxxxxxxx>
• Re: How to implement live migration of VMs in thinlv after using lvmlockd
  • From: Zhiyong Ye <yezhiyong@xxxxxxxxxxxxx>
• Re: How to implement live migration of VMs in thinlv after using lvmlockd
  • From: Stuart D Gathman <stuart@xxxxxxxxxxx>
• Re: How to implement live migration of VMs in thinlv after using lvmlockd
  • From: Demi Marie Obenour <demi@xxxxxxxxxxxxxxxxxxxxxx>
• Re: How to implement live migration of VMs in thinlv after using lvmlockd
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: How to implement live migration of VMs in thinlv after using lvmlockd
  • From: David Teigland <teigland@xxxxxxxxxx>
• How to implement live migration of VMs in thinlv after using lvmlockd
  • From: Zhiyong Ye <yezhiyong@xxxxxxxxxxxxx>
• Re: lvs activation columns are confusing for shared volume groups
  • From: David Teigland <teigland@xxxxxxxxxx>
• lvs activation columns are confusing for shared volume groups
  • From: corubba <corubba@xxxxxx>
• Re: [EXTERNAL] Re: LVM2 : performance drop even after deleting the snapshot
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: [EXTERNAL] Re: LVM2 : performance drop even after deleting the snapshot
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: [EXTERNAL] Re: LVM2 : performance drop even after deleting the snapshot
  • From: Erwin van Londen <erwin@xxxxxxxxxxxxxxxxxx>
• Re: [EXTERNAL] Re: LVM2 : performance drop even after deleting the snapshot
  • From: Pawan Sharma <sharmapawan@xxxxxxxxxxxxx>
• Re: LVM2 : performance drop even after deleting the snapshot
  • From: Demi Marie Obenour <demi@xxxxxxxxxxxxxxxxxxxxxx>
• Re: [EXTERNAL] Re: LVM2 : performance drop even after deleting the snapshot
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: LVM2 : performance drop even after deleting the snapshot
  • From: Kapil Upadhayay <kupadhayay@xxxxxxxxxxxxx>
• Re: [EXTERNAL] Re: LVM2 : performance drop even after deleting the snapshot
  • From: Mitta Sai Chaithanya <mittas@xxxxxxxxxxxxx>
• Re: LVM2 : performance drop even after deleting the snapshot
  • From: Roberto Fastec <roberto.fastec@xxxxxxxxx>
• Re: LVM2 : performance drop even after deleting the snapshot
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re: LVM2 : performance drop even after deleting the snapshot
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: LVM2 : performance drop even after deleting the snapshot
  • From: Pawan Sharma <sharmapawan@xxxxxxxxxxxxx>
• LVM2 : performance drop even after deleting the snapshot
  • From: Pawan Sharma <sharmapawan@xxxxxxxxxxxxx>
• Re: LVM2 Metadata structure, extents ordering, metadata corruptions
  • From: Roberto Fastec <roberto.fastec@xxxxxxxxx>
• Re: LVM2 Metadata structure, extents ordering, metadata corruptions
  • From: Roberto Fastec <roberto.fastec@xxxxxxxxx>
• Re: How to change default system dir
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re: LVM2 Metadata structure, extents ordering, metadata corruptions
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: LVM2 Metadata structure, extents ordering, metadata corruptions
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: How to change default system dir
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: LVM2 Metadata structure, extents ordering, metadata corruptions
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• LVM2 Metadata structure, extents ordering, metadata corruptions
  • From: Roberto Fastec <roberto.fastec@xxxxxxxxx>
• How to change default system dir
  • From: Bartłomiej Błachut <bartlomiejblachut@xxxxxxxxx>
• Re: lvcreate hangs forever during snapshot creation when suspending volume
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: lvcreate hangs forever during snapshot creation when suspending volume
  • From: Thomas Deutschmann <whissi@xxxxxxxxx>
• Re: lvmpolld causes high cpu load issue
  • From: Heming Zhao <heming.zhao@xxxxxxxx>
• Re: lvmpolld causes high cpu load issue
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• Re: lvmpolld causes high cpu load issue
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• Re: lvmpolld causes high cpu load issue
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• Re: lvmpolld causes high cpu load issue
  • From: Heming Zhao <heming.zhao@xxxxxxxx>
• lvmpolld causes IO performance issue
  • From: Heming Zhao <heming.zhao@xxxxxxxx>
• lvmpolld causes high cpu load issue
  • From: Heming Zhao <heming.zhao@xxxxxxxx>
• Re: lvmpolld causes high cpu load issue
  • From: Heming Zhao <heming.zhao@xxxxxxxx>
• Re: lvmpolld causes high cpu load issue
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• Re: lvmpolld causes high cpu load issue
  • From: Martin Wilck <martin.wilck@xxxxxxxx>
• Re: lvmpolld causes high cpu load issue
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: lvmpolld causes high cpu load issue
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: lvmpolld causes high cpu load issue
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: lvmpolld causes high cpu load issue
  • From: Demi Marie Obenour <demi@xxxxxxxxxxxxxxxxxxxxxx>
• Re: lvmpolld causes high cpu load issue
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: lvmpolld causes high cpu load issue
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: lvmpolld causes high cpu load issue
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: lvmpolld causes high cpu load issue
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: lvmpolld causes high cpu load issue
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: lvmpolld causes high cpu load issue
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: lvmpolld causes high cpu load issue
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: lvmpolld causes IO performance issue
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: Creating/restoring snapshots in early userspace
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: Creating/restoring snapshots in early userspace
  • From: cd <cd@terminal.space>
• Re: Creating/restoring snapshots in early userspace
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: Problem with partially activate logical volume
  • From: Ken Bass <daytooner@xxxxxxxxx>
• Creating/restoring snapshots in early userspace
  • From: cd <cd@terminal.space>
• Re: Problem with partially activate logical volume
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: Problem with partially activate logical volume
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re: Problem with partially activate logical volume
  • From: Ken Bass <daytooner@xxxxxxxxx>
• Re: raidintegrity on non top level LVs
  • From: ajs124 <linux-lvm@xxxxxxxxx>
• Re: raidintegrity on non top level LVs
  • From: David Teigland <teigland@xxxxxxxxxx>
• raidintegrity on non top level LVs
  • From: ajs124 <linux-lvm@xxxxxxxxx>
• Re: lvcreate hangs forever during snapshot creation when suspending volume
  • From: "Thomas Deutschmann" <whissi@xxxxxxxxx>
• Re: lvcreate hangs forever during snapshot creation when suspending volume
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: lvcreate hangs forever during snapshot creation when suspending volume
  • From: "Thomas Deutschmann" <whissi@xxxxxxxxx>
• Re: lvcreate hangs forever during snapshot creation when suspending volume
  • From: "Thomas Deutschmann" <whissi@xxxxxxxxx>
• Re: lvcreate hangs forever during snapshot creation when suspending volume
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: lvcreate hangs forever during snapshot creation when suspending volume
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• lvcreate hangs forever during snapshot creation when suspending volume
  • From: "Thomas Deutschmann" <whissi@xxxxxxxxx>
• Re: Problem with partially activate logical volume
  • From: Roger James <roger@xxxxxxxxxxxxxxxxxxxxx>
• Re: Problem with partially activate logical volume
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: Problem with partially activate logical volume
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re: Problem with partially activate logical volume
  • From: Roger James <roger@xxxxxxxxxxxxxxxxxxxxx>
• Re: Where are the data blocks of an LV?
  • From: Roger James <roger@xxxxxxxxxxxxxxxxxxxxx>
• Re: Where are the data blocks of an LV?
  • From: Stuart D Gathman <stuart@xxxxxxxxxxx>
• Problem with partially activate logical volume
  • From: Ken Bass <daytooner@xxxxxxxxx>
• Fix for Bug 2109351 - multipath_component_detection = 0 in lvm.conf does not have any effect
  • From: "Marappan, Gopinath" <Gopinath.Marappan@xxxxxxxx>
• Where are the data blocks of an LV?
  • From: Marcin Owsiany <marcin@xxxxxxxxxx>
• Re: Recovering from a failed pvmove
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re: Recovering from a failed pvmove
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re: Recovering from a failed pvmove
  • From: Roger James <roger@xxxxxxxxxxxxxxxxxxxxx>
• Recovering from a failed pvmove
  • From: Roger James <roger@xxxxxxxxxxxxxxxxxxxxx>
• Re: Why is the performance of my lvmthin snapshot so poor
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Why is the performance of my lvmthin snapshot so poor
  • From: Demi Marie Obenour <demi@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Why is the performance of my lvmthin snapshot so poor
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Why is the performance of my lvmthin snapshot so poor
  • From: Demi Marie Obenour <demi@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Why is the performance of my lvmthin snapshot so poor
  • From: Zhiyong Ye <yezhiyong@xxxxxxxxxxxxx>
• Re: Why is the performance of my lvmthin snapshot so poor
  • From: Zhiyong Ye <yezhiyong@xxxxxxxxxxxxx>
• Re: Why is the performance of my lvmthin snapshot so poor
  • From: Demi Marie Obenour <demi@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Why is the performance of my lvmthin snapshot so poor
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Why is the performance of my lvmthin snapshot so poor
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Why is the performance of my lvmthin snapshot so poor
  • From: Zhiyong Ye <yezhiyong@xxxxxxxxxxxxx>
• Re: Why is the performance of my lvmthin snapshot so poor
  • From: Zhiyong Ye <yezhiyong@xxxxxxxxxxxxx>
• Re: Why is the performance of my lvmthin snapshot so poor
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Why is the performance of my lvmthin snapshot so poor
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Why is the performance of my lvmthin snapshot so poor
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Why is the performance of my lvmthin snapshot so poor
  • From: Zhiyong Ye <yezhiyong@xxxxxxxxxxxxx>
• Re: lvm commands hanging when run from inside a kubernetes pod
  • From: Demi Marie Obenour <demi@xxxxxxxxxxxxxxxxxxxxxx>
• Re: lvm commands hanging when run from inside a kubernetes pod
  • From: Bernd Eckenfels <ecki@xxxxxxxxxxxxxxxxx>
• Re: lvm commands hanging when run from inside a kubernetes pod
  • From: Abhishek Agarwal <mragarwal.developer@xxxxxxxxx>
• dm-cache / lvmcache - no cleanup for dirty data in writeback/cleaner mode
  • From: CoolCold <coolthecold@xxxxxxxxx>
• Re: lvm commands hanging when run from inside a kubernetes pod
  • From: Demi Marie Obenour <demi@xxxxxxxxxxxxxxxxxxxxxx>
• Re: lvm commands hanging when run from inside a kubernetes pod
  • From: Abhishek Agarwal <mragarwal.developer@xxxxxxxxx>
• Re: lvm commands hanging when run from inside a kubernetes pod
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re: lvm commands hanging when run from inside a kubernetes pod
  • From: Nir Soffer <nsoffer@xxxxxxxxxx>
• Re: lvm commands hanging when run from inside a kubernetes pod
  • From: Abhishek Agarwal <mragarwal.developer@xxxxxxxxx>
• Re: raid10 with missing redundancy, but health status claims it is ok.
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: lvm commands hanging when run from inside a kubernetes pod
  • From: Demi Marie Obenour <demi@xxxxxxxxxxxxxxxxxxxxxx>
• Re: lvm commands hanging when run from inside a kubernetes pod
  • From: Abhishek Agarwal <mragarwal.developer@xxxxxxxxx>
• Re: raid10 with missing redundancy, but health status claims it is ok.
  • From: Olaf Seibert <o.seibert@xxxxxxxxxxxx>
• Re: lvm commands hanging when run from inside a kubernetes pod
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re: lvm commands hanging when run from inside a kubernetes pod
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: raid10 with missing redundancy, but health status claims it is ok.
  • From: Demi Marie Obenour <demi@xxxxxxxxxxxxxxxxxxxxxx>
• Re: raid10 with missing redundancy, but health status claims it is ok.
  • From: Olaf Seibert <o.seibert@xxxxxxxxxxxx>
• Re: raid10 with missing redundancy, but health status claims it is ok.
  • From: Olaf Seibert <o.seibert@xxxxxxxxxxxx>
• lvm commands hanging when run from inside a kubernetes pod
  • From: Abhishek Agarwal <mragarwal.developer@xxxxxxxxx>
• Re: raid10 with missing redundancy, but health status claims it is ok.
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• raid10 with missing redundancy, but health status claims it is ok.
  • From: Olaf Seibert <o.seibert@xxxxxxxxxxxx>
• Re: The lvm partiton size is not accurate
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• The lvm partiton size is not accurate
  • From: "Yu, Mingli" <Mingli.Yu@xxxxxxxxxxxxx>
• Re: vgcreate doesn't work with lvmlockd running
  • From: Zhiyong Ye <yezhiyong@xxxxxxxxxxxxx>
• Re: Bypassing LVM Restrictions - RAID6 With Less Than 5 Disks
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: Bypassing LVM Restrictions - RAID6 With Less Than 5 Disks
  • From: Stuart D Gathman <stuart@xxxxxxxxxxx>
• Re: Bypassing LVM Restrictions - RAID6 With Less Than 5 Disks
  • From: Alex Lieflander <atlief@xxxxxxxxxx>
• Re: Bypassing LVM Restrictions - RAID6 With Less Than 5 Disks
  • From: Stuart D Gathman <stuart@xxxxxxxxxxx>
• Re: Bypassing LVM Restrictions - RAID6 With Less Than 5 Disks
  • From: Alex Lieflander <atlief@xxxxxxxxxx>
• Re: Silence Pool Check Overprovisioning Warnings
  • From: Demi Marie Obenour <demi@xxxxxxxxxxxxxxxxxxxxxx>
• Silence Pool Check Overprovisioning Warnings
  • From: Robert Simmons <rsimmons0@xxxxxxxxx>
• Re: vgcreate doesn't work with lvmlockd running
  • From: David Teigland <teigland@xxxxxxxxxx>
• vgcreate doesn't work with lvmlockd running
  • From: Zhiyong Ye <yezhiyong@xxxxxxxxxxxxx>
• Re: Bypassing LVM Restrictions - RAID6 With Less Than 5 Disks
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: Bypassing LVM Restrictions - RAID6 With Less Than 5 Disks
  • From: Alex Lieflander <atlief@xxxxxxxxxx>
• Re: Bypassing LVM Restrictions - RAID6 With Less Than 5 Disks
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Bypassing LVM Restrictions - RAID6 With Less Than 5 Disks
  • From: Alex Lieflander <atlief@xxxxxxxxxx>
• [PATCH] misc: use getrandom(GRND_INSECURE) instead of /dev/urandom when possible
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Running multiple LVM commands in a batch
  • From: Demi Marie Obenour <demi@xxxxxxxxxxxxxxxxxxxxxx>
• [PATCH 2/3] Disable lvm2 udev rules if `dmsetup splitname` fails
  • From: Demi Marie Obenour <demi@xxxxxxxxxxxxxxxxxxxxxx>
• [PATCH 1/3] dmsetup: return non-zero on stdio I/O error
  • From: Demi Marie Obenour <demi@xxxxxxxxxxxxxxxxxxxxxx>
• [PATCH 3/3] Disable udev rules if udev flags can't be obtained
  • From: Demi Marie Obenour <demi@xxxxxxxxxxxxxxxxxxxxxx>
• [PATCH 2/3] Disable lvm2 udev rules if `dmsetup splitname` fails
  • From: Demi Marie Obenour <demi@xxxxxxxxxxxxxxxxxxxxxx>
• [PATCH 1/3] dmsetup: return non-zero on stdio I/O error
  • From: Demi Marie Obenour <demi@xxxxxxxxxxxxxxxxxxxxxx>
• [PATCH 0/3] Make udev rules more robust
  • From: Demi Marie Obenour <demi@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Safety of DM_DISABLE_UDEV=1 and --noudevsync
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Safety of DM_DISABLE_UDEV=1 and --noudevsync
  • From: Demi Marie Obenour <demi@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Frequent crashes when accessing dev_name(dev) on an empty list
  • From: Konstantin Kharlamov <hi-angel@xxxxxxxxx>
• Re: LVM autoactivation and udev
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: LVM autoactivation and udev
  • From: "heming.zhao@xxxxxxxx" <heming.zhao@xxxxxxxx>
• Re: LVM autoactivation and udev
  • From: "heming.zhao@xxxxxxxx" <heming.zhao@xxxxxxxx>
• Re: LVM autoactivation and udev
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: LVM autoactivation and udev
  • From: "heming.zhao@xxxxxxxx" <heming.zhao@xxxxxxxx>
• Re: LVM autoactivation and udev
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: LVM autoactivation and udev
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: LVM autoactivation and udev
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: LVM autoactivation and udev
  • From: Martin Wilck <mwilck@xxxxxxxx>
• LVM autoactivation and udev
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: LVM autoactivation and udev
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: LVM autoactivation and udev
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: LVM autoactivation and udev
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: LVM autoactivation and udev
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re: LVM autoactivation and udev
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: LVM fast mode
  • From: David Teigland <teigland@xxxxxxxxxx>
• LVM fast mode
  • From: Demi Marie Obenour <demi@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Need inputs: Performance issues with LVM snapshots
  • From: Demi Marie Obenour <demi@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Need inputs: Performance issues with LVM snapshots
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Need inputs: Performance issues with LVM snapshots
  • From: "Gaikwad, Hemant" <H.Gaikwad@xxxxxxxx>
• LVM limits
  • From: Christian Blume <chr.blume@xxxxxxxxx>
• Re: Cannot manage FS of thin volume
  • From: Nicholas Geovanis <nickgeovanis@xxxxxxxxx>
• Cannot manage FS of thin volume
  • From: Viktor Trojanovic <viktor@xxxxxxxx>
• Re: Need information
  • From: Marian Csontos <mcsontos@xxxxxxxxxx>
• Re: Need information
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Need information
  • From: Gk Gk <ygk.kmr@xxxxxxxxx>
• Re: Frequent crashes when accessing dev_name(dev) on an empty list
  • From: Konstantin Kharlamov <hi-angel@xxxxxxxxx>
• Re: Frequent crashes when accessing dev_name(dev) on an empty list
  • From: David Teigland <teigland@xxxxxxxxxx>
• Frequent crashes when accessing dev_name(dev) on an empty list
  • From: Konstantin Kharlamov <hi-angel@xxxxxxxxx>
• Re: Thin pool performance when allocating lots of blocks
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: Thin pool performance when allocating lots of blocks
  • From: Demi Marie Obenour <demi@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Thin pool performance when allocating lots of blocks
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Thin pool performance when allocating lots of blocks
  • From: Demi Marie Obenour <demi@xxxxxxxxxxxxxxxxxxxxxx>
• Re: LVM performance vs direct dm-thin
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: LVM performance vs direct dm-thin
  • From: Demi Marie Obenour <demi@xxxxxxxxxxxxxxxxxxxxxx>
• Re: lvmdevices - impossible to remove/cleanup device
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: LVM performance vs direct dm-thin
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: LVM performance vs direct dm-thin
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• lvmdevices - impossible to remove/cleanup device
  • From: lejeczek <peljasz@xxxxxxxxxxx>
• Re: LVM performance vs direct dm-thin
  • From: Demi Marie Obenour <demi@xxxxxxxxxxxxxxxxxxxxxx>
• Re: LVM performance vs direct dm-thin
  • From: Demi Marie Obenour <demi@xxxxxxxxxxxxxxxxxxxxxx>
• Re: LVM performance vs direct dm-thin
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: LVM performance vs direct dm-thin
  • From: Marian Csontos <mcsontos@xxxxxxxxxx>
• Re: LVM performance vs direct dm-thin
  • From: Demi Marie Obenour <demi@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Running thin_trim before activating a thin pool
  • From: Demi Marie Obenour <demi@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Running thin_trim before activating a thin pool
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Running thin_trim before activating a thin pool
  • From: Demi Marie Obenour <demi@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Running thin_trim before activating a thin pool
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Running thin_trim before activating a thin pool
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: Running thin_trim before activating a thin pool
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Running thin_trim before activating a thin pool
  • From: Demi Marie Obenour <demi@xxxxxxxxxxxxxxxxxxxxxx>
• Re: LVM performance vs direct dm-thin
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: LVM performance vs direct dm-thin
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: LVM performance vs direct dm-thin
  • From: Demi Marie Obenour <demi@xxxxxxxxxxxxxxxxxxxxxx>
• Re: LVM performance vs direct dm-thin
  • From: "Stuart D. Gathman" <stuart@xxxxxxxxxxx>
• Re: LVM performance vs direct dm-thin
  • From: Demi Marie Obenour <demi@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Running thin_trim before activating a thin pool
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: LVM performance vs direct dm-thin
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Running thin_trim before activating a thin pool
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: Running thin_trim before activating a thin pool
  • From: Demi Marie Obenour <demi@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Running thin_trim before activating a thin pool
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: LVM performance vs direct dm-thin
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: Running thin_trim before activating a thin pool
  • From: Demi Marie Obenour <demi@xxxxxxxxxxxxxxxxxxxxxx>
• Re: LVM performance vs direct dm-thin
  • From: Demi Marie Obenour <demi@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Running thin_trim before activating a thin pool
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: LVM performance vs direct dm-thin
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: Running thin_trim before activating a thin pool
  • From: Demi Marie Obenour <demi@xxxxxxxxxxxxxxxxxxxxxx>
• Re: LVM performance vs direct dm-thin
  • From: Demi Marie Obenour <demi@xxxxxxxxxxxxxxxxxxxxxx>
• Re: LVM RAID behavior after losing physical disk
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: Running thin_trim before activating a thin pool
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: LVM performance vs direct dm-thin
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• LVM performance vs direct dm-thin
  • From: Demi Marie Obenour <demi@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Running thin_trim before activating a thin pool
  • From: Demi Marie Obenour <demi@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Running thin_trim before activating a thin pool
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Running thin_trim before activating a thin pool
  • From: Demi Marie Obenour <demi@xxxxxxxxxxxxxxxxxxxxxx>
• Re: LVM RAID behavior after losing physical disk
  • From: Andrei Rodionov <andrei.rodionov@xxxxxxxxx>
• Re: LVM RAID behavior after losing physical disk
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• LVM RAID behavior after losing physical disk
  • From: Andrei Rodionov <andrei.rodionov@xxxxxxxxx>
• Re: LVM pull requests?
  • From: David Teigland <teigland@xxxxxxxxxx>
• LVM pull requests?
  • From: Wayne Workman <wayne@xxxxxxxxxxxxxx>
• Re: LVM: Metadata on ... has wrong VG name
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: convert logical sector -> physical sector + pv/vg extent number
  • From: Stuart D Gathman <stuart@xxxxxxxxxxxxxxx>
• Re: Can't get merge in background using blockdev api to work
  • From: Tomas Dalebjörk <tomas.dalebjork@xxxxxxxxx>
• Re: Can't get merge in background using blockdev api to work
  • From: Vojtech Trefny <vtrefny@xxxxxxxxxx>
• Re: convert logical sector -> physical sector + pv/vg extent number
  • From: Roland <devzero@xxxxxx>
• Re: convert logical sector -> physical sector + pv/vg extent number
  • From: Roland <devzero@xxxxxx>
• Can't get merge in background using blockdev api to work
  • From: Tomas Dalebjörk <tomas.dalebjork@xxxxxxxxx>
• Re: convert logical sector -> physical sector + pv/vg extent number
  • From: Andy Smith <andy@xxxxxxxxxxxxxx>
• convert logical sector -> physical sector + pv/vg extent number
  • From: Roland <devzero@xxxxxx>
• Re: how to convert a disk containing a snapshot to a snapshot lv?
  • From: Stuart D Gathman <stuart@xxxxxxxxxxx>
• Re: how to convert a disk containing a snapshot to a snapshot lv?
  • From: Tomas Dalebjörk <tomas.dalebjork@xxxxxxxxx>
• Re: how to convert a disk containing a snapshot to a snapshot lv?
  • From: Stuart D Gathman <stuart@xxxxxxxxxxx>
• Re: LVM: Metadata on ... has wrong VG name
  • From: <linux-lvm@xxxxxxxxxx>
• Re: how to convert a disk containing a snapshot to a snapshot lv?
  • From: Tomas Dalebjörk <tomas.dalebjork@xxxxxxxxx>
• Re: how to convert a disk containing a snapshot to a snapshot lv?
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: how to convert a disk containing a snapshot to a snapshot lv?
  • From: Phillip Susi <phill@xxxxxxxxxxxx>
• Re: how to convert a disk containing a snapshot to a snapshot lv?
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: how to convert a disk containing a snapshot to a snapshot lv?
  • From: Tomas Dalebjörk <tomas.dalebjork@xxxxxxxxx>
• Re: how to convert a disk containing a snapshot to a snapshot lv?
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: LVM: Metadata on ... has wrong VG name
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: how to convert a disk containing a snapshot to a snapshot lv?
  • From: Phillip Susi <phill@xxxxxxxxxxxx>
• Re: size of lvm metadata
  • From: Tomas Dalebjörk <tomas.dalebjork@xxxxxxxxx>
• LVM: Metadata on ... has wrong VG name
  • From: <linux-lvm@xxxxxxxxxx>
• how to convert a disk containing a snapshot to a snapshot lv?
  • From: Tomas Dalebjörk <tomas.dalebjork@xxxxxxxxx>
• Re: Reason to use -r when systemd-run vgchange -aay
  • From: Tom Yan <tom.ty89@xxxxxxxxx>
• Re: Reason to use -r when systemd-run vgchange -aay
  • From: David Teigland <teigland@xxxxxxxxxx>
• Reason to use -r when systemd-run vgchange -aay
  • From: Tom Yan <tom.ty89@xxxxxxxxx>
• Re: LVM Thin - bad checksum in superblock - cannot perform operations on metadata
  • From: Ming-Hung Tsai <mingnus@xxxxxxxxx>
• Re: (resend) may bug: lvconvert reports "Insufficient free space" when doing "--replace"
  • From: "heming.zhao@xxxxxxxx" <heming.zhao@xxxxxxxx>
• LVM Thin - bad checksum in superblock - cannot perform operations on metadata
  • From: pavel olenev <pavel.olenev@xxxxxxxxx>
• Re: Replace Drive in RAID6
  • From: Adam Puleo <adam.puleo@xxxxxxxxxx>
• Have tested dm-raid/lv mirroring with block guard on one leg but not the other, it fails to mirror the disk
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re: "md/raid:mdX: cannot start dirty degraded array."
  • From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
• Re: (resend) may bug: lvconvert reports "Insufficient free space" when doing "--replace"
  • From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
• Re: Replace Drive in RAID6
  • From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
• Re: Replace Drive in RAID6
  • From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>