Linux LVM

• Thread Index

• Re: Check of pool ernie/cache failed (status:1). Manual repair required!
  • From: Dennis Schridde <devurandom@xxxxxxx>
• Re: Check of pool ernie/cache failed (status:1). Manual repair required!
  • From: Marian Csontos <mcsontos@xxxxxxxxxx>
• Re: "write failed.. No space left", "Failed to write VG", and "Failed to write a MDA"
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: "write failed.. No space left", "Failed to write VG", and "Failed to write a MDA"
  • From: Jim Haddad <jimhaddad46@xxxxxxxxx>
• Re: "write failed.. No space left", "Failed to write VG", and "Failed to write a MDA"
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: "write failed.. No space left", "Failed to write VG", and "Failed to write a MDA"
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: Check of pool ernie/cache failed (status:1). Manual repair required!
  • From: Dennis Schridde <devurandom@xxxxxxx>
• Re: "write failed.. No space left", "Failed to write VG", and "Failed to write a MDA"
  • From: Inbox <jimhaddad46@xxxxxxxxx>
• "write failed.. No space left", "Failed to write VG", and "Failed to write a MDA"
  • From: Inbox <jimhaddad46@xxxxxxxxx>
• Re: "write failed.. No space left", "Failed to write VG", and "Failed to write a MDA"
  • From: Inbox <jimhaddad46@xxxxxxxxx>
• Re: "write failed.. No space left", "Failed to write VG", and "Failed to write a MDA"
  • From: Patrick Mitchell <patricklmitchell9@xxxxxxxxx>
• Re: "write failed.. No space left", "Failed to write VG", and "Failed to write a MDA"
  • From: Jim Haddad <jimhaddad46@xxxxxxxxx>
• Re: "write failed.. No space left", "Failed to write VG", and "Failed to write a MDA"
  • From: Jim Haddad <jimhaddad46@xxxxxxxxx>
• Re: "write failed.. No space left", "Failed to write VG", and "Failed to write a MDA"
  • From: Inbox <jimhaddad46@xxxxxxxxx>
• Re: "write failed.. No space left", "Failed to write VG", and "Failed to write a MDA"
  • From: Inbox <jimhaddad46@xxxxxxxxx>
• Re: Device XXX excluded by a filter - why??
  • From: Damon Wang <damon.devops@xxxxxxxxx>
• Re: pvmove does not work at all with version 2.02.177(2)
  • From: "Gang He" <ghe@xxxxxxxx>
• Re: [RELEASE] 2.02.178
  • From: "Gang He" <ghe@xxxxxxxx>
• Re: pvmove does not work at all with version 2.02.177(2)
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: [lvmlockd] "VGLK res_unlock lm error -250" and lvm command hung forever
  • From: Damon Wang <damon.devops@xxxxxxxxx>
• Re: Device XXX excluded by a filter - why??
  • From: Marian Csontos <mcsontos@xxxxxxxxxx>
• Re: [RELEASE] 2.02.178
  • From: Marian Csontos <mcsontos@xxxxxxxxxx>
• Re: pvmove does not work at all with version 2.02.177(2)
  • From: Marian Csontos <mcsontos@xxxxxxxxxx>
• pvmove does not work at all with version 2.02.177(2)
  • From: "Gang He" <ghe@xxxxxxxx>
• Re: Move LV with GFS to new LUN (pvmove) in the cluster
  • From: kAja Ziegler <ziegleka@xxxxxxxxx>
• Re: lvcreate cannot create a mirrored LV with version 2.02.177(2)
  • From: "Gang He" <ghe@xxxxxxxx>
• Re: Check of pool ernie/cache failed (status:1). Manual repair required!
  • From: Dennis Schridde <devurandom@xxxxxxx>
• Re: lvcreate cannot create a mirrored LV with version 2.02.177(2)
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: [RELEASE] 2.02.178
  • From: "Gang He" <ghe@xxxxxxxx>
• lvcreate cannot create a mirrored LV with version 2.02.177(2)
  • From: "Gang He" <ghe@xxxxxxxx>
• [RELEASE] 2.02.178
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: [lvmlockd] "VGLK res_unlock lm error -250" and lvm command hung forever
  • From: Damon Wang <damon.devops@xxxxxxxxx>
• Re: [lvmlockd] "VGLK res_unlock lm error -250" and lvm command hung forever
  • From: David Teigland <teigland@xxxxxxxxxx>
• [lvmlockd] "VGLK res_unlock lm error -250" and lvm command hung forever
  • From: Damon Wang <damon.devops@xxxxxxxxx>
• Re: Move LV with GFS to new LUN (pvmove) in the cluster
  • From: emmanuel segura <emi2fast@xxxxxxxxx>
• Device XXX excluded by a filter - why??
  • From: Wyllys Ingersoll <wyllys.ingersoll@xxxxxxxxxxxxxx>
• Move LV with GFS to new LUN (pvmove) in the cluster
  • From: kAja Ziegler <ziegleka@xxxxxxxxx>
• Re: Check of pool ernie/cache failed (status:1). Manual repair required!
  • From: Dennis Schridde <devurandom@xxxxxxx>
• Re: Can't work normally after attaching disk volumes originally in a VG on another machine
  • From: "Gang He" <ghe@xxxxxxxx>
• Re: [PATCH] lib/device/bcache: don't use PAGE_SIZE
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: inconsistency between thin pool metadata mapped_blocks and lvs output
  • From: John Hamilton <john.l.hamilton@xxxxxxxxx>
• [PATCH] lib/device/bcache: don't use PAGE_SIZE
  • From: Alex Bennée <alex.bennee@xxxxxxxxxx>
• Re: pvscan takes 45-90 minutes booting off ISO with thin pools
  • From: Patrick Mitchell <patricklmitchell9@xxxxxxxxx>
• Re: pvscan takes 45-90 minutes booting off ISO with thin pools
  • From: Patrick Mitchell <patricklmitchell9@xxxxxxxxx>
• Re: Check of pool ernie/cache failed (status:1). Manual repair required!
  • From: Dennis Schridde <devurandom@xxxxxxx>
• Re: Check of pool ernie/cache failed (status:1). Manual repair required!
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Check of pool ernie/cache failed (status:1). Manual repair required!
  • From: Dennis Schridde <devurandom@xxxxxxx>
• Re: how to set higher then 128 nr_requests on LV's
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: how to set higher then 128 nr_requests on LV's
  • From: Pankaj Agarwal <pankaj@xxxxxxxxxxxxxxxxx>
• Re: how to set higher then 128 nr_requests on LV's
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: how to set higher then 128 nr_requests on LV's
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: how to set higher then 128 nr_requests on LV's
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• how to set higher then 128 nr_requests on LV's
  • From: Pankaj Agarwal <pankaj@xxxxxxxxxxxxxxxxx>
• Re: inconsistency between thin pool metadata mapped_blocks and lvs output
  • From: John Hamilton <john.l.hamilton@xxxxxxxxx>
• pvscan takes 45-90 minutes booting off ISO with thin pools
  • From: Patrick Mitchell <patricklmitchell9@xxxxxxxxx>
• Re: Check of pool ernie/cache failed (status:1). Manual repair required!
  • From: Dennis Schridde <devurandom@xxxxxxx>
• Check of pool ernie/cache failed (status:1). Manual repair required!
  • From: Dennis Schridde <devurandom@xxxxxxx>
• Re: inconsistency between thin pool metadata mapped_blocks and lvs output
  • From: Marian Csontos <mcsontos@xxxxxxxxxx>
• Re: inconsistency between thin pool metadata mapped_blocks and lvs output
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• inconsistency between thin pool metadata mapped_blocks and lvs output
  • From: John Hamilton <john.l.hamilton@xxxxxxxxx>
• LVM not activated on boot in linux mdraid (Fedora 28)
  • From: Patrick Dung <mpatdung@xxxxxxxxx>
• Re: api recommandation (example_cmdlib.c doesnt work properly)?
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• api recommandation (example_cmdlib.c doesnt work properly)?
  • From: Oliver Rath <rath@xxxxxxxx>
• Re: Pvmove can work on cluster with LVM 2.02.120(2) (2015-05-15), or not?
  • From: "Gang He" <ghe@xxxxxxxx>
• Re: Pvmove can work on cluster with LVM 2.02.120(2) (2015-05-15), or not?
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: [lvmlockd] Reload configuration while lvmlockd and sanlock running
  • From: Damon Wang <damon.devops@xxxxxxxxx>
• Re: Pvmove can work on cluster with LVM 2.02.120(2) (2015-05-15), or not?
  • From: "Gang He" <ghe@xxxxxxxx>
• Re: [lvmlockd] Reload configuration while lvmlockd and sanlock running
  • From: David Teigland <teigland@xxxxxxxxxx>
• Pvmove can work on cluster with LVM 2.02.120(2) (2015-05-15), or not?
  • From: Gang He <dchg2000@xxxxxxxxx>
• [lvmlockd] Reload configuration while lvmlockd and sanlock running
  • From: Damon Wang <damon.devops@xxxxxxxxx>
• Re: Add udev-md-raid-safe-timeouts.rules
  • From: "Austin S. Hemmelgarn" <ahferroin7@xxxxxxxxx>
• Re: Add udev-md-raid-safe-timeouts.rules
  • From: "Austin S. Hemmelgarn" <ahferroin7@xxxxxxxxx>
• Re: Add udev-md-raid-safe-timeouts.rules
  • From: Alan Stern <stern@xxxxxxxxxxxxxxxxxxx>
• Re: Add udev-md-raid-safe-timeouts.rules
  • From: "Wol's lists" <antlists@xxxxxxxxxxxxxxx>
• Re: Add udev-md-raid-safe-timeouts.rules
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Add udev-md-raid-safe-timeouts.rules
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re: Add udev-md-raid-safe-timeouts.rules
  • From: "Austin S. Hemmelgarn" <ahferroin7@xxxxxxxxx>
• Add udev-md-raid-safe-timeouts.rules
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: "Data alignment must not exceed device size."
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: "Data alignment must not exceed device size."
  • From: "Richard W.M. Jones" <rjones@xxxxxxxxxx>
• Re: "Data alignment must not exceed device size."
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: "Data alignment must not exceed device size."
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: "Data alignment must not exceed device size."
  • From: "Richard W.M. Jones" <rjones@xxxxxxxxxx>
• Re: "Data alignment must not exceed device size."
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: "Data alignment must not exceed device size."
  • From: "Richard W.M. Jones" <rjones@xxxxxxxxxx>
• "Data alignment must not exceed device size."
  • From: "Richard W.M. Jones" <rjones@xxxxxxxxxx>
• Re: compile lvm2 with --enable-lvmlockd-sanlock on Ubuntu 1710, configure failed. For help, thanks
  • From: Guozhonghua <guozhonghua@xxxxxxx>
• Re: PVmove can not work on lvm2-2.02.177
  • From: "Gang He" <ghe@xxxxxxxx>
• Re: PVmove can not work on lvm2-2.02.177
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• PVmove can not work on lvm2-2.02.177
  • From: "Gang He" <ghe@xxxxxxxx>
• Re: compile lvm2 with --enable-lvmlockd-sanlock on Ubuntu 1710, configure failed. For help, thanks
  • From: "Gang He" <ghe@xxxxxxxx>
• compile lvm2 with --enable-lvmlockd-sanlock on Ubuntu 1710, configure failed. For help, thanks
  • From: Guozhonghua <guozhonghua@xxxxxxx>
• Re: Cannot create PV on /dev/dm-NN (/dev/dm-N works)
  • From: Michael Fladischer <michael@xxxxxxxx>
• Re: Cannot create PV on /dev/dm-NN (/dev/dm-N works)
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re: Can't work normally after attaching disk volumes originally in a VG on another machine
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: Cannot create PV on /dev/dm-NN (/dev/dm-N works)
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Cannot create PV on /dev/dm-NN (/dev/dm-N works)
  • From: Michael Fladischer <michael@xxxxxxxx>
• Re: Can't work normally after attaching disk volumes originally in a VG on another machine
  • From: "Gang He" <ghe@xxxxxxxx>
• Re: Can't work normally after attaching disk volumes originally in a VG on another machine
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: Higher than expected metadata usage?
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Higher than expected metadata usage?
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Higher than expected metadata usage?
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Higher than expected metadata usage?
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Higher than expected metadata usage?
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Can't work normally after attaching disk volumes originally in a VG on another machine
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: Can't work normally after attaching disk volumes originally in a VG on another machine
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: Higher than expected metadata usage?
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Higher than expected metadata usage?
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Can't work normally after attaching disk volumes originally in a VG on another machine
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: Can't work normally after attaching disk volumes originally in a VG on another machine
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Higher than expected metadata usage?
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Higher than expected metadata usage?
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Can't work normally after attaching disk volumes originally in a VG on another machine
  • From: "Gang He" <ghe@xxxxxxxx>
• Re: Can't work normally after attaching disk volumes originally in a VG on another machine
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: Can't work normally after attaching disk volumes originally in a VG on another machine
  • From: Fran Garcia <fran@xxxxxxxxxxxxxxx>
• Re: Can't work normally after attaching disk volumes originally in a VG on another machine
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Can't work normally after attaching disk volumes originally in a VG on another machine
  • From: Fran Garcia <franchu.garcia@xxxxxxxxx>
• Re: Can't work normally after attaching disk volumes originally in a VG on another machine
  • From: "Gang He" <ghe@xxxxxxxx>
• Re: Can't work normally after attaching disk volumes originally in a VG on another machine
  • From: Xen <list@xxxxxxxxxxxxx>
• Can't work normally after attaching disk volumes originally in a VG on another machine
  • From: "Gang He" <ghe@xxxxxxxx>
• Re: [lvmlockd] Refresh lvmlockd leases after sanlock changes
  • From: Damon Wang <damon.devops@xxxxxxxxx>
• Re: Fix lvm2 build against musl libc
  • From: Bjorn Pagen <bjornpagen@xxxxxxxxx>
• Fix lvm2 build against musl libc
  • From: bjornpagen@xxxxxxxxx
• Re: [lvmlockd] Refresh lvmlockd leases after sanlock changes
  • From: Damon Wang <damon.devops@xxxxxxxxx>
• Re: [lvmlockd] Refresh lvmlockd leases after sanlock changes
  • From: Damon Wang <damon.devops@xxxxxxxxx>
• Re: [lvmlockd] Refresh lvmlockd leases after sanlock changes
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• [lvmlockd] Refresh lvmlockd leases after sanlock changes
  • From: Damon Wang <damon.devops@xxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Gianluca Cecchi <gianluca.cecchi@xxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Xen <list@xxxxxxxxxxxxx>
• replacing missing disk thin pool raid1
  • From: Etienne Champetier <champetier.etienne@xxxxxxxxx>
• Re: Saying goodbye to LVM
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: Saying goodbye to LVM
  • From: matthew patton <pattonme@xxxxxxxxx>
• Re: Saying goodbye to LVM
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Saying goodbye to LVM
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: Saying goodbye to LVM
  • From: pattonme@xxxxxxxxx
• Re: Saying goodbye to LVM
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Unsync-ed LVM Mirror
  • From: Eric Ren <zren@xxxxxxxx>
• bogus WARNING Device for PV not found or rejected by a filter
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• bogus WARNING: Device for PV not found or rejected by a filter.
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Unsync-ed LVM Mirror
  • From: Liwei <xieliwei@xxxxxxxxx>
• Re: Unsync-ed LVM Mirror
  • From: Eric Ren <zren@xxxxxxxx>
• Re: Unsync-ed LVM Mirror
  • From: Liwei <xieliwei@xxxxxxxxx>
• Re: Unsync-ed LVM Mirror
  • From: Eric Ren <zren@xxxxxxxx>
• Re: Unsync-ed LVM Mirror
  • From: Liwei <xieliwei@xxxxxxxxx>
• Unsync-ed LVM Mirror
  • From: Liwei <xieliwei@xxxxxxxxx>
• Re: Saying goodbye to LVM
  • From: John Stoffel <john@xxxxxxxxxxx>
• Saying goodbye to LVM
  • From: Xen <list@xxxxxxxxxxxxx>
• pvscan hung in LVM 160
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: lvmlockd: about the limitation on lvresizing the LV active on multiple nodes
  • From: Eric Ren <zren@xxxxxxxx>
• Re: unable to exclude LVs using global_filter
  • From: Gordon Messmer <gordon.messmer@xxxxxxxxx>
• Re: The benefits of lvmlockd over clvmd?
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: new max tag length?
  • From: Oliver Rath <rath@xxxxxxxx>
• Re: The benefits of lvmlockd over clvmd?
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: lvmlockd: about the limitation on lvresizing the LV active on multiple nodes
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: The benefits of lvmlockd over clvmd?
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: The benefits of lvmlockd over clvmd?
  • From: Eric Ren <zren@xxxxxxxx>
• Re: The benefits of lvmlockd over clvmd?
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: The benefits of lvmlockd over clvmd?
  • From: Eric Ren <zren@xxxxxxxx>
• Re: lvmlockd: about the limitation on lvresizing the LV active on multiple nodes
  • From: Eric Ren <zren@xxxxxxxx>
• Re: The benefits of lvmlockd over clvmd?
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: lvmlockd: about the limitation on lvresizing the LV active on multiple nodes
  • From: David Teigland <teigland@xxxxxxxxxx>
• The benefits of lvmlockd over clvmd?
  • From: Eric Ren <zren@xxxxxxxx>
• Re: lvmlockd: about the limitation on lvresizing the LV active on multiple nodes
  • From: Eric Ren <zren@xxxxxxxx>
• Re: new max tag length?
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• new max tag length?
  • From: Oliver Rath <rath@xxxxxxxx>
• Re: lvmlockd: about the limitation on lvresizing the LV active on multiple nodes
  • From: Eric Ren <zren@xxxxxxxx>
• Re: unable to exclude LVs using global_filter
  • From: Gordon Messmer <gordon.messmer@xxxxxxxxx>
• Re: lvmlockd: about the limitation on lvresizing the LV active on multiple nodes
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: lvmlockd: about the limitation on lvresizing the LV active on multiple nodes
  • From: Eric Ren <zren@xxxxxxxx>
• Re: unable to exclude LVs using global_filter
  • From: Gordon Messmer <gordon.messmer@xxxxxxxxx>
• Re: unable to exclude LVs using global_filter
  • From: Gordon Messmer <gordon.messmer@xxxxxxxxx>
• Re: unable to exclude LVs using global_filter
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: unable to exclude LVs using global_filter
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: unable to exclude LVs using global_filter
  • From: Marian Csontos <mcsontos@xxxxxxxxxx>
• Re: lvmlockd: about the limitation on lvresizing the LV active on multiple nodes
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: lvmlockd manpage: prevent concurrent activation of logical volumes?
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: unable to exclude LVs using global_filter
  • From: Gordon Messmer <gordon.messmer@xxxxxxxxx>
• Re: unable to exclude LVs using global_filter
  • From: Marian Csontos <mcsontos@xxxxxxxxxx>
• Re: lvmlockd: about the limitation on lvresizing the LV active on multiple nodes
  • From: Eric Ren <zren@xxxxxxxx>
• unable to exclude LVs using global_filter
  • From: Gordon Messmer <gordon.messmer@xxxxxxxxx>
• Re: Migrate volumes to new laptop
  • From: Eric Ren <zren@xxxxxxxx>
• Re: Migrate volumes to new laptop
  • From: Bernd Eckenfels <ecki@xxxxxxxxxxxxxxxxx>
• Problems with linking lvm statically with musl
  • From: KARBOWSKI Piotr <piotr.karbowski@xxxxxxxxx>
• lvmlockd: about the limitation on lvresizing the LV active on multiple nodes
  • From: Eric Ren <zren@xxxxxxxx>
• lvmlockd manpage: prevent concurrent activation of logical volumes?
  • From: Eric Ren <zren@xxxxxxxx>
• fallocate for thin volumes?
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Migrate volumes to new laptop
  • From: Boyd Kelly <bkelly@xxxxxxxxxxxxxxxx>
• LVM doesn't resume the origin if it failed to take a dm-thin snapshot
  • From: Ming-Hung Tsai <mingnus@xxxxxxxxx>
• Re: lvm filter regex format
  • From: Thanos Makatos <thanos.makatos@xxxxxxxxx>
• Re: lvm filter regex format
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: lvm filter regex format
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: lvm filter regex format
  • From: matthew patton <pattonme@xxxxxxxxx>
• Re: lvm filter regex format
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• lvm filter regex format
  • From: Thanos Makatos <thanos.makatos@xxxxxxxxx>
• Re: lvm filter not ignoring block device
  • From: Thanos Makatos <thanos.makatos@xxxxxxxxx>
• Re: lvm filter not ignoring block device
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• lvm filter not ignoring block device
  • From: Thanos Makatos <thanos.makatos@xxxxxxxxx>
• cache performance
  • From: Xen <list@xxxxxxxxxxxxx>
• SOLVED [was: lvmdbusd failure(s) at ubuntu]
  • From: Oliver Rath <rath@xxxxxxxx>
• Re: LVM2 - pvresize alert
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• LVM2 - pvresize alert
  • From: VESELÍK Jan <jveselik@xxxxxxx>
• More logs [was: lvmdbusd failure(s) at ubuntu ]
  • From: Oliver Rath <rath@xxxxxxxx>
• More logs [was: Re: addendum [was: lvmdbusd failure(s) at ubuntu ]]
  • From: Oliver Rath <rath@xxxxxxxx>
• More logs [was: Re: addendum [was: lvmdbusd failure(s) at ubuntu ]]
  • From: Oliver Rath <rath@xxxxxxxx>
• Re: addendum [was: lvmdbusd failure(s) at ubuntu ]
  • From: Marian Csontos <mcsontos@xxxxxxxxxx>
• Re: lvmdbusd failure(s) at ubuntu
  • From: Marian Csontos <mcsontos@xxxxxxxxxx>
• addendum [was: lvmdbusd failure(s) at ubuntu ]
  • From: Oliver Rath <rath@xxxxxxxx>
• lvmdbusd failure(s) at ubuntu
  • From: Oliver Rath <rath@xxxxxxxx>
• Re: lvreduce ignores --test for implicit BLKDISCARD?
  • From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@xxxxxxx>
• lvreduce ignores --test for implicit BLKDISCARD?
  • From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@xxxxxxx>
• Re: Why LVM doesn't send the dm-thin delete message immediately after volume creation failure
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Why LVM doesn't send the dm-thin delete message immediately after volume creation failure
  • From: Ming-Hung Tsai <mingnus@xxxxxxxxx>
• Re: Shared VG, Separate LVs
  • From: Indivar Nair <indivar.nair@xxxxxxxxxxxx>
• Re: Shared VG, Separate LVs
  • From: Eric Ren <zren@xxxxxxxx>
• Re: Reattach cache
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Reattach cache
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: Reattach cache
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: Reattach cache
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Reattach cache
  • From: matthew patton <pattonme@xxxxxxxxx>
• Reattach cache
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: Shared VG, Separate LVs
  • From: Indivar Nair <indivar.nair@xxxxxxxxxxxx>
• Re: lvmlockd: how to convert lock_type from sanlock to dlm?
  • From: Eric Ren <zren@xxxxxxxx>
• Re: lvmlockd: how to convert lock_type from sanlock to dlm?
  • From: David Teigland <teigland@xxxxxxxxxx>
• lvmlockd: how to convert lock_type from sanlock to dlm?
  • From: Eric Ren <zren@xxxxxxxx>
• Strange behavior
  • From: Georges Giralt <georges.giralt@xxxxxxx>
• Re: LVM hangs
  • From: "Alexander 'Leo' Bergolth" <leo@xxxxxxxxxxxxxxx>
• Re: LVM hangs
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: LVM hangs
  • From: "Alexander 'Leo' Bergolth" <leo@xxxxxxxxxxxxxxx>
• Re: lvremove try to remove a WRONG logic volume!!!
  • From: Peter Rajnoha <prajnoha@xxxxxxxxxx>
• lvremove try to remove a WRONG logic volume!!!
  • From: BaiLin Times <balintimes@xxxxxxxxx>
• Re: Shared VG, Separate LVs
  • From: Eric Ren <zren@xxxxxxxx>
• Re: LVM hangs
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: LVM hangs
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: LVM hangs
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: LVM hangs
  • From: "Alexander 'Leo' Bergolth" <leo@xxxxxxxxxxxxxxx>
• Re: LVM hangs
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• LVM hangs
  • From: "Alexander 'Leo' Bergolth" <leo@xxxxxxxxxxxxxxx>
• Re: Maximum number of drives in a Logical Volume Stripe
  • From: Indivar Nair <indivar.nair@xxxxxxxxxxxx>
• Re: When and why vgs command can change metadata and incur old metadata to be backed up?
  • From: Eric Ren <zren@xxxxxxxx>
• Re: Question on mixing technologies
  • From: Georges Giralt <georges.giralt@xxxxxxx>
• Maximum number of drives in a Logical Volume Stripe
  • From: Indivar Nair <indivar.nair@xxxxxxxxxxxx>
• Re: Shared VG, Separate LVs
  • From: Indivar Nair <indivar.nair@xxxxxxxxxxxx>
• Recover LVM Volume Group when 2 physical disks removed
  • From: Traiano Welcome <traiano@xxxxxxxxx>
• Does cmirror can tolerate one faulty PV?
  • From: Eric Ren <zren@xxxxxxxx>
• 答复: [dm-devel] dmsetup hangs forever
  • From: "Zhangyanfei (YF)" <yanfei.zhang@xxxxxxxxxx>
• Re: When and why vgs command can change metadata and incur old metadata to be backed up?
  • From: Eric Ren <zren@xxxxxxxx>
• Re: When and why vgs command can change metadata and incur old metadata to be backed up?
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: When and why vgs command can change metadata and incur old metadata to be backed up?
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: When and why vgs command can change metadata and incur old metadata to be backed up?
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: When and why vgs command can change metadata and incur old metadata to be backed up?
  • From: David Teigland <teigland@xxxxxxxxxx>
• When and why vgs command can change metadata and incur old metadata to be backed up?
  • From: Eric Ren <zren@xxxxxxxx>
• Re: 答复: [dm-devel] dmsetup hangs forever
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: unable to recover from degraded raid1 with thin pool
  • From: "Alexander 'Leo' Bergolth" <leo@xxxxxxxxxxxxxxx>
• Re: [dm-devel] dmsetup hangs forever
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• dmsetup hangs forever
  • From: "Zhangyanfei (YF)" <yanfei.zhang@xxxxxxxxxx>
• Re: lvm raid: pvmove vs lvconvert
  • From: lejeczek <peljasz@xxxxxxxxxxx>
• Re: unable to remove snapshot of raid1 leg
  • From: "Alexander 'Leo' Bergolth" <leo@xxxxxxxxxxxxxxx>
• Re: cache on SSD makes system unresponsive
  • From: Chris Friesen <chris.friesen@xxxxxxxxxxxxx>
• Re: cache on SSD makes system unresponsive
  • From: matthew patton <pattonme@xxxxxxxxx>
• Re: lvm raid: pvmove vs lvconvert
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: cache on SSD makes system unresponsive
  • From: Oleg Cherkasov <o1e9@xxxxxxxxxxxxxx>
• Re: cache on SSD makes system unresponsive
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: cache on SSD makes system unresponsive
  • From: lejeczek <peljasz@xxxxxxxxxxx>
• Re: unable to remove snapshot of raid1 leg
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: cache on SSD makes system unresponsive
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: cache on SSD makes system unresponsive
  • From: matthew patton <pattonme@xxxxxxxxx>
• Re: cache on SSD makes system unresponsive
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: cache on SSD makes system unresponsive
  • From: matthew patton <pattonme@xxxxxxxxx>
• Re: cache on SSD makes system unresponsive
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: unable to remove snapshot of raid1 leg
  • From: "Alexander 'Leo' Bergolth" <leo@xxxxxxxxxxxxxxx>
• Re: unable to remove snapshot of raid1 leg
  • From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
• Re: unable to remove snapshot of raid1 leg
  • From: "Alexander 'Leo' Bergolth" <leo@xxxxxxxxxxxxxxx>
• unable to remove snapshot of raid1 leg
  • From: "Alexander 'Leo' Bergolth" <leo@xxxxxxxxxxxxxxx>
• Re: unable to recover from degraded raid1 with thin pool
  • From: "Alexander 'Leo' Bergolth" <leo@xxxxxxxxxxxxxxx>
• Re: cache on SSD makes system unresponsive
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: cache on SSD makes system unresponsive
  • From: matthew patton <pattonme@xxxxxxxxx>
• Re: cache on SSD makes system unresponsive
  • From: matthew patton <pattonme@xxxxxxxxx>
• Re: cache on SSD makes system unresponsive
  • From: Oleg Cherkasov <o1e9@xxxxxxxxxxxxxx>
• Re: cache on SSD makes system unresponsive
  • From: Oleg Cherkasov <o1e9@xxxxxxxxxxxxxx>
• Re: cache on SSD makes system unresponsive
  • From: Bernd Eckenfels <ecki@xxxxxxxxxxxxxxxxx>
• Re: cache on SSD makes system unresponsive
  • From: Joe Thornber <joe.thornber@xxxxxxxxx>
• Re: cache on SSD makes system unresponsive
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: cache on SSD makes system unresponsive
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: unable to recover from degraded raid1 with thin pool (was: activation mode=degraded doesn't work with thin pool)
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: cache on SSD makes system unresponsive
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: cache on SSD makes system unresponsive
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: cache on SSD makes system unresponsive
  • From: lejeczek <peljasz@xxxxxxxxxxx>
• Re: cache on SSD makes system unresponsive
  • From: Oleg Cherkasov <o1e9@xxxxxxxxxxxxxx>
• Re: cache on SSD makes system unresponsive
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: cache on SSD makes system unresponsive
  • From: Oleg Cherkasov <o1e9@xxxxxxxxxxxxxx>
• Re: cache on SSD makes system unresponsive
  • From: Oleg Cherkasov <o1e9@xxxxxxxxxxxxxx>
• cache on SSD makes system unresponsive
  • From: Oleg Cherkasov <olegc@xxxxxxxxxxxx>
• Re: cache on SSD makes system unresponsive
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: cache on SSD makes system unresponsive
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: cache on SSD makes system unresponsive
  • From: matthew patton <pattonme@xxxxxxxxx>
• Re: cache on SSD makes system unresponsive
  • From: Oleg Cherkasov <o1e9@xxxxxxxxxxxxxx>
• Re: cache on SSD makes system unresponsive
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: cache on SSD makes system unresponsive
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: cache on SSD makes system unresponsive
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: cache on SSD makes system unresponsive
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: cache on SSD makes system unresponsive
  • From: Xen <list@xxxxxxxxxxxxx>
• cache on SSD makes system unresponsive
  • From: Oleg Cherkasov <o1e9@xxxxxxxxxxxxxx>
• unable to recover from degraded raid1 with thin pool (was: activation mode=degraded doesn't work with thin pool)
  • From: "Alexander 'Leo' Bergolth" <leo@xxxxxxxxxxxxxxx>
• Re: raid10 to raid what? - convert
  • From: lejeczek <peljasz@xxxxxxxxxxx>
• Re: raid10 to raid what? - convert
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: raid10 to raid what? - convert
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: raid10 to raid what? - convert
  • From: lejeczek <peljasz@xxxxxxxxxxx>
• Re: lvm raid: pvmove vs lvconvert
  • From: lejeczek <peljasz@xxxxxxxxxxx>
• lvm raid: pvmove vs lvconvert
  • From: lejeczek <peljasz@xxxxxxxxxxx>
• Re: raid10 to raid what? - convert
  • From: "Stuart D. Gathman" <stuart@xxxxxxxxxxx>
• Re: raid10 to raid what? - convert
  • From: Tanstaafl <tanstaafl@xxxxxxxxxxxxxxx>
• Re: raid10 to raid what? - convert
  • From: "Stuart D. Gathman" <stuart@xxxxxxxxxxx>
• Re: raid10 to raid what? - convert
  • From: "Stuart D. Gathman" <stuart@xxxxxxxxxxx>
• Re: add_lockspace done -19
  • From: David Teigland <teigland@xxxxxxxxxx>
• activation mode=degraded doesn't work with thin pool
  • From: "Alexander 'Leo' Bergolth" <leo@xxxxxxxxxxxxxxx>
• Re: raid10 to raid what? - convert
  • From: lejeczek <peljasz@xxxxxxxxxxx>
• Re: add_lockspace done -19
  • From: Moshe Lazarov <Moshe.Lazarov@xxxxxxxxxx>
• Re: add_lockspace done -19
  • From: Moshe Lazarov <Moshe.Lazarov@xxxxxxxxxx>
• Re: raid10 to raid what? - convert
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: add_lockspace done -19
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: Shared VG, Separate LVs
  • From: Indivar Nair <indivar.nair@xxxxxxxxxxxx>
• Re: Shared VG, Separate LVs
  • From: Eric Ren <zren@xxxxxxxx>
• raid10 to raid what? - convert
  • From: lejeczek <peljasz@xxxxxxxxxxx>
• Re: add_lockspace done -19
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: Shared VG, Separate LVs
  • From: Eric Ren <zren@xxxxxxxx>
• add_lockspace done -19
  • From: Moshe Lazarov <Moshe.Lazarov@xxxxxxxxxx>
• Shared VG, Separate LVs
  • From: Indivar Nair <indivar.nair@xxxxxxxxxxxx>
• Re: Difference between Debian and some other distributions with thin provisioning
  • From: Jan Tulak <jtulak@xxxxxxxxxx>
• Re: Difference between Debian and some other distributions with thin provisioning
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Difference between Debian and some other distributions with thin provisioning
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Difference between Debian and some other distributions with thin provisioning
  • From: Xen <list@xxxxxxxxxxxxx>
• Difference between Debian and some other distributions with thin provisioning
  • From: Jan Tulak <jtulak@xxxxxxxxxx>
• Re: lvm raid1 metadata on different pv
  • From: "Alexander 'Leo' Bergolth" <leo@xxxxxxxxxxxxxxx>
• Re: lvm raid1 metadata on different pv
  • From: emmanuel segura <emi2fast@xxxxxxxxx>
• Re: lvm raid1 metadata on different pv
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: raid & its stripes
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• lvm raid1 metadata on different pv
  • From: "Alexander 'Leo' Bergolth" <leo@xxxxxxxxxxxxxxx>
• Re: raid & its stripes
  • From: lejeczek <peljasz@xxxxxxxxxxx>
• Re: raid & its stripes
  • From: lejeczek <peljasz@xxxxxxxxxxx>
• Re: Restoring snapshot gone bad
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Restoring snapshot gone bad
  • From: Xen <list@xxxxxxxxxxxxx>
• Restoring snapshot gone bad
  • From: Mauricio Tavares <raubvogel@xxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Xen <list@xxxxxxxxxxxxx>
• Clarification (and limitation) of the kernel feature I proposed
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: Option to silence "WARNING: Sum of all thin volume sizes exceeds the size of thin pool"
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: Option to silence "WARNING: Sum of all thin volume sizes exceeds the size of thin pool"
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Option to silence "WARNING: Sum of all thin volume sizes exceeds the size of thin pool"
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Option to silence "WARNING: Sum of all thin volume sizes exceeds the size of thin pool"
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Option to silence "WARNING: Sum of all thin volume sizes exceeds the size of thin pool"
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: Option to silence "WARNING: Sum of all thin volume sizes exceeds the size of thin pool"
  • From: matthew patton <pattonme@xxxxxxxxx>
• Re: Option to silence "WARNING: Sum of all thin volume sizes exceeds the size of thin pool"
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Option to silence "WARNING: Sum of all thin volume sizes exceeds the size of thin pool"
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Option to silence "WARNING: Sum of all thin volume sizes exceeds the size of thin pool"
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Option to silence "WARNING: Sum of all thin volume sizes exceeds the size of thin pool"
  • From: matthew patton <pattonme@xxxxxxxxx>
• Re: Option to silence "WARNING: Sum of all thin volume sizes exceeds the size of thin pool"
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Option to silence "WARNING: Sum of all thin volume sizes exceeds the size of thin pool"
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Option to silence "WARNING: Sum of all thin volume sizes exceeds the size of thin pool"
  • From: David Teigland <teigland@xxxxxxxxxx>
• Option to silence "WARNING: Sum of all thin volume sizes exceeds the size of thin pool"
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: raid & its stripes
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: pvscan: bugs in manpage and implementation
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: pvscan: bugs in manpage and implementation
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• pvscan: bugs in manpage and implementation
  • From: Tom Hale <tom@xxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: raid & its stripes
  • From: lejeczek <peljasz@xxxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: matthew patton <pattonme@xxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: raid & its stripes
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: raid & its stripes
  • From: lejeczek <peljasz@xxxxxxxxxxx>
• Re: Performance penalty for 4k requests on thin provisioned volume
  • From: Dale Stephenson <dalestephenson@xxxxxxx>
• Re: raid & its stripes
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: Performance penalty for 4k requests on thin provisioned volume
  • From: Dale Stephenson <dalestephenson@xxxxxxx>
• Re: Performance penalty for 4k requests on thin provisioned volume
  • From: Gionatan Danti <assistenza@xxxxxxxxxx>
• Re: Performance penalty for 4k requests on thin provisioned volume
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Performance penalty for 4k requests on thin provisioned volume
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Performance penalty for 4k requests on thin provisioned volume
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Performance penalty for 4k requests on thin provisioned volume
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: Performance penalty for 4k requests on thin provisioned volume
  • From: Dale Stephenson <dalestephenson@xxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: matthew patton <pattonme@xxxxxxxxx>
• Re: Performance penalty for 4k requests on thin provisioned volume
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Xen <list@xxxxxxxxxxxxx>
• Performance penalty for 4k requests on thin provisioned volume
  • From: Dale Stephenson <dalestephenson@xxxxxxx>
• raid & its stripes
  • From: lejeczek <peljasz@xxxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: matthew patton <pattonme@xxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: matthew patton <pattonme@xxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: matthew patton <pattonme@xxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: matthew patton <pattonme@xxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: matthew patton <pattonme@xxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: pattonme@xxxxxxxxx
• Re: Reserve space for specific thin logical volumes
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: matthew patton <pattonme@xxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Eric Ren <zren@xxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Eric Ren <zren@xxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Eric Ren <zren@xxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: lv raid - how to read this?
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Reserve space for specific thin logical volumes
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: lv raid - how to read this?
  • From: Ming-Hung Tsai <mingnus@xxxxxxxxx>
• Re: lv raid - how to read this?
  • From: Ming-Hung Tsai <mingnus@xxxxxxxxx>
• Re: lv raid - how to read this?
  • From: lejeczek <peljasz@xxxxxxxxxxx>
• Reserve space for specific thin logical volumes
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: lv raid - how to read this?
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: lv raid - how to read this?
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: lv raid - how to read this?
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: lv raid - how to read this?
  • From: lejeczek <peljasz@xxxxxxxxxxx>
• Re: lv raid - how to read this?
  • From: lejeczek <peljasz@xxxxxxxxxxx>
• Re: lv raid - how to read this?
  • From: lejeczek <peljasz@xxxxxxxxxxx>
• Re: lv raid - how to read this?
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: lv raid - how to read this?
  • From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
• Re: lv raid - how to read this?
  • From: lejeczek <peljasz@xxxxxxxxxxx>
• Re: lv raid - how to read this?
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• lv raid - how to read this?
  • From: lejeczek <peljasz@xxxxxxxxxxx>
• Re: Distributed Locking of LVM
  • From: Peter Rajnoha <prajnoha@xxxxxxxxxx>
• Re: Distributed Locking of LVM
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: Distributed Locking of LVM
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Distributed Locking of LVM
  • From: Kalyana sundaram <kalyanceg@xxxxxxxxx>
• Re: Distributed Locking of LVM
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: Distributed Locking of LVM
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Distributed Locking of LVM
  • From: Digimer <lists@xxxxxxxxxx>
• Distributed Locking of LVM
  • From: Kalyana sundaram <kalyanceg@xxxxxxxxx>
• lvm2-2.02.173 breaks Slackware-current systems with snapshots
  • From: TPClvm@xxxxxxxxxxxxxxxxxxx
• Re: How to compile lvm with lvmlockd
  • From: Ravi Hemnani <raviiihemnani@xxxxxxxxx>
• Re: How to compile lvm with lvmlockd
  • From: David Teigland <teigland@xxxxxxxxxx>
• How to compile lvm with lvmlockd
  • From: Ravi Hemnani <raviiihemnani@xxxxxxxxx>
• recursion in lvol prepared as physical partittion
  • From: Herman Rohenkohl <H.Rohenkohl@xxxxxxxxx>
• SOLVED [ was Re: logical "and" connection of lvm-tags? ]
  • From: Oliver Rath <rath@xxxxxxxx>
• Re: logical "and" connection of lvm-tags?
  • From: Peter Rajnoha <prajnoha@xxxxxxxxxx>
• Re: LVM archive management ( /etc/lvm/archives) expiry / retention misbehaves after index #100, 000.
  • From: Mark Mielke <mark.mielke@xxxxxxxxx>
• LVM archive management ( /etc/lvm/archives) expiry / retention misbehaves after index #100, 000.
  • From: Mark Mielke <mark.mielke@xxxxxxxxx>
• logical "and" connection of lvm-tags?
  • From: Oliver Rath <rath@xxxxxxxx>
• possibly off-topic - multipath
  • From: lejeczek <peljasz@xxxxxxxxxxx>
• Re: dm-cache size is limited by 946GB
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: BUG: unable to handle kernel NULL pointer dereference in notifier_call_chain
  • From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH 1/2] dmsetup: add support to output devices in bootformat style
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: lvmetad crashes with “memory smash” during lvm parallel operations
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: dm-cache size is limited by 946GB
  • From: CoolCold <coolthecold@xxxxxxxxx>
• Re: dm-cache size is limited by 946GB
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• BUG: unable to handle kernel NULL pointer dereference in notifier_call_chain
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• lvmetad crashes with “memory smash” during lvm parallel operations
  • From: "Shivarama Krishnan, Gururaj (Nokia - IN/Bangalore)" <gururaj.shivarama_krishnan@xxxxxxxxx>
• Re: lvmetad crashes with “memory smash” during lvm parallel operations
  • From: "Shivarama Krishnan, Gururaj (Nokia - IN/Bangalore)" <gururaj.shivarama_krishnan@xxxxxxxxx>
• dm-cache size is limited by 946GB
  • From: CoolCold <coolthecold@xxxxxxxxx>
• raid0 extends?
  • From: lejeczek <peljasz@xxxxxxxxxxx>
• Re: convert LV to physical device _in_place_?
  • From: Stuart Gathman <stuart@xxxxxxxxxxx>
• Re: convert LV to physical device _in_place_?
  • From: Marek Podmaka <marki@xxxxxxxxxxxxxxxx>
• Re: convert LV to physical device _in_place_?
  • From: Matthias Leopold <matthias.leopold@xxxxxxxxxxxxxxxx>
• Re: convert LV to physical device _in_place_?
  • From: "Stuart D. Gathman" <stuart@xxxxxxxxxxx>
• Re: convert LV to physical device _in_place_?
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• convert LV to physical device _in_place_?
  • From: Matthias Leopold <matthias.leopold@xxxxxxxxxxxxxxxx>
• Alert emails for degraded LVs
  • From: Billy Crook <billycrook@xxxxxxxxx>
• Unable to determine sync status errror when trying split LVM2 RAID 1 mirror
  • From: Faheem Mitha <faheem@xxxxxxxxxxx>
• Re: [PATCH v8 0/2] dm: boot a mapped device without an initramfs
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: Problem with mount QNAP disks in Linux
  • From: Danniello <danniello@xxxxxxxxx>
• Re: Problem with mount QNAP disks in Linux
  • From: Marian Csontos <mcsontos@xxxxxxxxxx>
• Re: deadlock during backup from lvm snapshot
  • From: Jack Wang <jack.wang.usish@xxxxxxxxx>
• Re: LVM send/receive support?
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: LVM send/receive support?
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: LVM send/receive support?
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• LVM send/receive support?
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Problem with mount QNAP disks in Linux
  • From: Daniel Łaskowski <danniello@xxxxxxxxx>
• Re: Question on mixing technologies
  • From: Stuart Gathman <stuart@xxxxxxxxxxx>
• Re: Question on mixing technologies
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: Question on mixing technologies
  • From: Georges Giralt <georges.giralt@xxxxxxx>
• Re: lvm.conf parameter for PVs to use for lvcreate ?
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• lvm.conf parameter for PVs to use for lvcreate ?
  • From: Oliver Rath <rath@xxxxxxxx>
• [PATCH v8 1/2] init: add support to directly boot to a mapped device
  • From: Enric Balletbo i Serra <enric.balletbo@xxxxxxxxxxxxx>
• [PATCH v8 2/2] dm ioctl: add a device mapper ioctl function.
  • From: Enric Balletbo i Serra <enric.balletbo@xxxxxxxxxxxxx>
• [PATCH v8 0/2] dm: boot a mapped device without an initramfs
  • From: Enric Balletbo i Serra <enric.balletbo@xxxxxxxxxxxxx>
• Re: [dm-devel] [PATCH v7 0/2] dm: boot a mapped device without an initramfs
  • From: Enric Balletbo Serra <eballetbo@xxxxxxxxx>
• [PATCH v7 2/2] dm ioctl: add a device mapper ioctl function.
  • From: Enric Balletbo i Serra <enric.balletbo@xxxxxxxxxxxxx>
• [PATCH v7 1/2] init: add support to directly boot to a mapped device
  • From: Enric Balletbo i Serra <enric.balletbo@xxxxxxxxxxxxx>
• [PATCH v7 0/2] dm: boot a mapped device without an initramfs
  • From: Enric Balletbo i Serra <enric.balletbo@xxxxxxxxxxxxx>
• [PATCH v2 1/3] libdm: Add dm_find_unescaped_char to libdevmapper.
  • From: Enric Balletbo i Serra <enric.balletbo@xxxxxxxxxxxxx>
• [PATCH v2 2/3] dmsetup: add support to output devices in bootformat style
  • From: Enric Balletbo i Serra <enric.balletbo@xxxxxxxxxxxxx>
• [PATCH v2 0/3] dmsetup: add bootformat support
  • From: Enric Balletbo i Serra <enric.balletbo@xxxxxxxxxxxxx>
• [PATCH v2 3/3] dmsetup: add support to create devices when bootformat is used
  • From: Enric Balletbo i Serra <enric.balletbo@xxxxxxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Howto change cachepolicy on cached thinpool devices?
  • From: Oliver Rath <rath@xxxxxxxx>
• Re: Howto change cachepolicy on cached thinpool devices?
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Howto change cachepolicy on cached thinpool devices?
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Howto change cachepolicy on cached thinpool devices?
  • From: Oliver Rath <rath@xxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: on discards
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• on discards
  • From: Xen <list@xxxxxxxxxxxxx>
• SOLVED [was: : pvmove of thinpool-metadata fail]
  • From: Oliver Rath <rath@xxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• pvmove of thinpool-metadata fail
  • From: Oliver Rath <rath@xxxxxxxx>
• Re: Question on mixing technologies
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Question on mixing technologies
  • From: Georges Giralt <georges.giralt@xxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Sector size is assumed 512
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Sector size is assumed 512
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Sector size is assumed 512
  • From: Tomasz Lasko <tomasz@xxxxxxxx>
• Re: lvm/openstack: stripe all volumes and distribute them round robin on PVs
  • From: Bernd Eckenfels <ecki@xxxxxxxxxxxxxxxxx>
• deadlock during backup from lvm snapshot
  • From: Sergey Zhuravlev <sergey@xxxxxxxxx>
• Re: configure fail with option --enable-notivy-dbus
  • From: "Bryn M. Reeves" <bmr@xxxxxxxxxx>
• Re: configure fail with option --enable-notivy-dbus
  • From: Oliver Rath <rath@xxxxxxxx>
• Re: configure fail with option --enable-notivy-dbus
  • From: Oliver Rath <rath@xxxxxxxx>
• Re: configure fail with option --enable-notivy-dbus
  • From: "Bryn M. Reeves" <bmr@xxxxxxxxxx>
• Re: configure fail with option --enable-notivy-dbus
  • From: Marian Csontos <mcsontos@xxxxxxxxxx>
• configure fail with option --enable-notivy-dbus
  • From: Oliver Rath <rath@xxxxxxxx>
• Re: lvm/openstack: stripe all volumes and distribute them round robin on PVs
  • From: David Teigland <teigland@xxxxxxxxxx>
• configure error with dbus-flags
  • From: Oliver Rath <rath@xxxxxxxx>
• lvm/openstack: stripe all volumes and distribute them round robin on PVs
  • From: Bernd <ecki@xxxxxxxxxxxxxxxxx>
• [PATCH 0/2] dmsetup: add bootformat support
  • From: Enric Balletbo i Serra <enric.balletbo@xxxxxxxxxxxxx>
• [PATCH 2/2] dmsetup: add support to create devices when bootformat is used
  • From: Enric Balletbo i Serra <enric.balletbo@xxxxxxxxxxxxx>
• [PATCH 1/2] dmsetup: add support to output devices in bootformat style
  • From: Enric Balletbo i Serra <enric.balletbo@xxxxxxxxxxxxx>
• Different stripesize on thinpool/thinlv + config issue
  • From: Oliver Rath <rath@xxxxxxxx>
• suspend to disk and LVM cache corruption
  • From: Piotr Pawłow <pp@xxxxxxxxxxx>
• lvconvert --merge invalidating snapshot
  • From: Luke Bigum <luke.bigum@xxxxxxxx>
• Addendum: [was different stripesize on thinpool/thinlv]
  • From: Oliver Rath <rath@xxxxxxxx>
• different stripesize on thinpool/thinlv
  • From: Oliver Rath <rath@xxxxxxxx>
• Configuration of stripes in lvm.conf?
  • From: Oliver Rath <rath@xxxxxxxx>
• Apparent race condition with srp and diskless machine
  • From: "Mervini, Joseph A" <jamervi@xxxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• init script 'command not found error'
  • From: Sen Han <hansen3032@xxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Stuart Gathman <stuart@xxxxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Stuart Gathman <stuart@xxxxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: VG won't activate -- dm problem
  • From: Scott Hazelhurst <Scott.Hazelhurst@xxxxxxxxxx>
• Proper way to remove a qemu-nbd-mounted volume using lvm
  • From: Leroy Tennison <leroy.tennison@xxxxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Xen <list@xxxxxxxxxxxxx>
• VG won't activate -- dm problem
  • From: Scott Hazelhurst <Scott.Hazelhurst@xxxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: new multipath device mistakenly replaced another PV in existing volume group
  • From: matthew patton <pattonme@xxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: new multipath device mistakenly replaced another PV in existing volume group
  • From: Neutron Sharc <neutronsharc@xxxxxxxxx>
• Re: new multipath device mistakenly replaced another PV in existing volume group
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: new multipath device mistakenly replaced another PV in existing volume group
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: ubuntu xenial + lvmlockd
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: ubuntu xenial + lvmlockd
  • From: Charles Koprowski <cko@xxxxxxxxxxx>
• Re: clvm: failed to activate logical volumes sometimes
  • From: emmanuel segura <emi2fast@xxxxxxxxx>
• Re: clvm: failed to activate logical volumes sometimes
  • From: Eric Ren <zren@xxxxxxxx>
• Re: clvm: failed to activate logical volumes sometimes
  • From: emmanuel segura <emi2fast@xxxxxxxxx>
• Re: clvm: failed to activate logical volumes sometimes
  • From: Eric Ren <zren@xxxxxxxx>
• new multipath device mistakenly replaced another PV in existing volume group
  • From: Neutron Sharc <neutronsharc@xxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: ubuntu xenial + lvmlockd
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: "Stuart D. Gathman" <stuart@xxxxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• clvm: failed to activate logical volumes sometimes
  • From: Eric Ren <zren@xxxxxxxx>
• ubuntu xenial + lvmlockd
  • From: Charles Koprowski <cko@xxxxxxxxxxx>
• root: Failed query for merging percentage. Aborting merge
  • From: Roger Morton <ttguy1@xxxxxxxxx>
• Re: root: Failed query for merging percentage. Aborting merge
  • From: Roger Morton <ttguy1@xxxxxxxxx>
• Re: thin volume usage report
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: thin volume usage report
  • From: Xen <list@xxxxxxxxxxxxx>
• thin volume usage report
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Xen <list@xxxxxxxxxxxxx>
• thin snapshot actual usage
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: Snapshot behavior on classic LVM vs ThinLVM
  • From: Stuart Gathman <stuart@xxxxxxxxxxx>