Linux LVM
[Prev Page][Next Page]
- Re: It looks wrong for the timeout when lvm test running
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- It looks wrong for the timeout when lvm test running
- From: Heming Zhao <heming.zhao@xxxxxxxx>
- Re: Best way to run LVM over multiple SW RAIDs?
- From: "John Stoffel" <john@xxxxxxxxxxx>
- Thin pool vg1-thinpool1-tpool (253:3) transaction_id is 549, while expected 505.
- From: Łukasz Czerpak <lukasz.czerpak@xxxxxxxxx>
- Re: Best way to run LVM over multiple SW RAIDs?
- From: Gionatan Danti <g.danti@xxxxxxxxxx>
- Re: Best way to run LVM over multiple SW RAIDs?
- From: "Stuart D. Gathman" <stuart@xxxxxxxxxxx>
- Re: Best way to run LVM over multiple SW RAIDs?
- From: "John Stoffel" <john@xxxxxxxxxxx>
- Re: Best way to run LVM over multiple SW RAIDs?
- From: "Stuart D. Gathman" <stuart@xxxxxxxxxxx>
- Re: Best way to run LVM over multiple SW RAIDs?
- From: Roberto Fastec <roberto.fastec@xxxxxxxxx>
- Re: Best way to run LVM over multiple SW RAIDs?
- From: Anatoly Pugachev <matorola@xxxxxxxxx>
- Question about vgreduce on raid lvm cache
- From: Heming Zhao <heming.zhao@xxxxxxxx>
- Re: resend patch - bcache may mistakenly write data to another disk when writes error
- From: David Teigland <teigland@xxxxxxxxxx>
- Re: resend patch - bcache may mistakenly write data to another disk when writes error
- From: David Teigland <teigland@xxxxxxxxxx>
- Re: exposing snapshot block device
- From: Tomas Dalebjörk <tomas.dalebjork@xxxxxxxxx>
- Re: exposing snapshot block device
- From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
- Re: exposing snapshot block device
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: exposing snapshot block device
- From: Tomas Dalebjörk <tomas.dalebjork@xxxxxxxxx>
- Re: exposing snapshot block device
- From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
- Re: exposing snapshot block device
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: exposing snapshot block device
- From: Tomas Dalebjörk <tomas.dalebjork@xxxxxxxxx>
- Re: exposing snapshot block device
- From: Tomas Dalebjörk <tomas.dalebjork@xxxxxxxxx>
- Re: exposing snapshot block device
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: exposing snapshot block device
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: exposing snapshot block device
- From: Tomas Dalebjörk <tomas.dalebjork@xxxxxxxxx>
- Re: bcache now to become io-manager?
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: bcache now to become io-manager?
- From: "John Stoffel" <john@xxxxxxxxxxx>
- Re: bcache now to become io-manager?
- From: Joe Thornber <thornber@xxxxxxxxxx>
- Re: bcache now to become io-manager?
- From: Marian Csontos <mcsontos@xxxxxxxxxx>
- bcache now to become io-manager?
- From: "John Stoffel" <john@xxxxxxxxxxx>
- Re: resend patch - bcache may mistakenly write data to another disk when writes error
- From: Joe Thornber <thornber@xxxxxxxxxx>
- Re: resend patch - bcache may mistakenly write data to another disk when writes error
- From: Heming Zhao <heming.zhao@xxxxxxxx>
- Re: resend patch - bcache may mistakenly write data to another disk when writes error
- From: Heming Zhao <heming.zhao@xxxxxxxx>
- Re: resend patch - bcache may mistakenly write data to another disk when writes error
- From: Joe Thornber <thornber@xxxxxxxxxx>
- Re: resend patch - bcache may mistakenly write data to another disk when writes error
- From: Joe Thornber <thornber@xxxxxxxxxx>
- Re: resend patch - bcache may mistakenly write data to another disk when writes error
- From: Heming Zhao <heming.zhao@xxxxxxxx>
- Best way to run LVM over multiple SW RAIDs?
- From: Daniel Janzon <daniel.janzon@xxxxxxxxxxx>
- Re: exposing snapshot block device
- From: Tomas Dalebjörk <tomas.dalebjork@xxxxxxxxx>
- Re: resend patch - bcache may mistakenly write data to another disk when writes error
- From: Heming Zhao <heming.zhao@xxxxxxxx>
- Re: resend patch - bcache may mistakenly write data to another disk when writes error
- From: Joe Thornber <thornber@xxxxxxxxxx>
- Re: resend patch - bcache may mistakenly write data to another disk when writes error
- From: Heming Zhao <heming.zhao@xxxxxxxx>
- Re: exposing snapshot block device
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: exposing snapshot block device
- From: Tomas Dalebjörk <tomas.dalebjork@xxxxxxxxx>
- Re: exposing snapshot block device
- From: Tomas Dalebjörk <tomas.dalebjork@xxxxxxxxx>
- Re: exposing snapshot block device
- From: Ilia Zykov <mail@xxxxxxxxxxx>
- Re: exposing snapshot block device
- From: Tomas Dalebjörk <tomas.dalebjork@xxxxxxxxx>
- Re: exposing snapshot block device
- From: Tomas Dalebjörk <tomas.dalebjork@xxxxxxxxx>
- Re: resend patch - bcache may mistakenly write data to another disk when writes error
- From: Heming Zhao <heming.zhao@xxxxxxxx>
- Re: resend patch - bcache may mistakenly write data to another disk when writes error
- From: Heming Zhao <heming.zhao@xxxxxxxx>
- Re: resend patch - bcache may mistakenly write data to another disk when writes error
- From: Joe Thornber <thornber@xxxxxxxxxx>
- Re: exposing snapshot block device
- From: Gionatan Danti <g.danti@xxxxxxxxxx>
- Re: exposing snapshot block device
- From: Ilia Zykov <mail@xxxxxxx>
- Re: exposing snapshot block device
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: exposing snapshot block device
- From: Gionatan Danti <g.danti@xxxxxxxxxx>
- Re: exposing snapshot block device
- From: Gionatan Danti <g.danti@xxxxxxxxxx>
- Re: exposing snapshot block device
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: exposing snapshot block device
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: exposing snapshot block device
- From: Ilia Zykov <mail@xxxxxxx>
- Re: exposing snapshot block device
- From: Gionatan Danti <g.danti@xxxxxxxxxx>
- Re: exposing snapshot block device
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: exposing snapshot block device
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: exposing snapshot block device
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: exposing snapshot block device
- From: Tomas Dalebjörk <tomas.dalebjork@xxxxxxxxx>
- Re: exposing snapshot block device
- From: Gionatan Danti <g.danti@xxxxxxxxxx>
- Re: exposing snapshot block device
- From: "Stuart D. Gathman" <stuart@xxxxxxxxxxx>
- Re: exposing snapshot block device
- From: Gionatan Danti <g.danti@xxxxxxxxxx>
- Re: exposing snapshot block device
- From: "Stuart D. Gathman" <stuart@xxxxxxxxxxx>
- Re: exposing snapshot block device
- From: Dalebjörk, Tomas <tomas.dalebjork@xxxxxxxxx>
- Re: exposing snapshot block device
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: exposing snapshot block device
- From: Dalebjörk, Tomas <tomas.dalebjork@xxxxxxxxx>
- Re: exposing snapshot block device
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- exposing snapshot block device
- From: Dalebjörk, Tomas <tomas.dalebjork@xxxxxxxxx>
- resend patch - bcache may mistakenly write data to another disk when writes error
- From: Heming Zhao <heming.zhao@xxxxxxxx>
- pvmove fails on VG, managed by PCS resource agent in HA-LVM mode(Active-Passive), with tagging enabled.
- From: Udai Sharma <udai.sharma5@xxxxxxxxx>
- pvmove fails on VG, managed by PCS resource agent in HA-LVM mode(Active-Passive), with tagging enabled.
- From: Udai Sharma <udai.sharma5@xxxxxxxxx>
- Re: pvresize will cause a meta-data corruption with error message "Error writing device at 4096 length 512"
- From: Heming Zhao <heming.zhao@xxxxxxxx>
- Re: recovery of a VG - how?
- From: lejeczek <peljasz@xxxxxxxxxxx>
- Re: recovery of a VG - how?
- From: lejeczek <peljasz@xxxxxxxxxxx>
- Re: devices/dir configuration option in /etc/lvm/lvm.conf can be edited?
- From: Gang He <GHe@xxxxxxxx>
- Re: devices/dir configuration option in /etc/lvm/lvm.conf can be edited?
- From: Alasdair G Kergon <agk@xxxxxxxxxx>
- Re: devices/dir configuration option in /etc/lvm/lvm.conf can be edited?
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: devices/dir configuration option in /etc/lvm/lvm.conf can be edited?
- From: Gang He <GHe@xxxxxxxx>
- Re: devices/dir configuration option in /etc/lvm/lvm.conf can be edited?
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- devices/dir configuration option in /etc/lvm/lvm.conf can be edited?
- From: Gang He <GHe@xxxxxxxx>
- Re: pvresize will cause a meta-data corruption with error message "Error writing device at 4096 length 512"
- From: Heming Zhao <heming.zhao@xxxxxxxx>
- Re: pvresize will cause a meta-data corruption with error message "Error writing device at 4096 length 512"
- From: Heming Zhao <heming.zhao@xxxxxxxx>
- Re: pvresize will cause a meta-data corruption with error message "Error writing device at 4096 length 512"
- From: Heming Zhao <heming.zhao@xxxxxxxx>
- Re: pvresize will cause a meta-data corruption with error message "Error writing device at 4096 length 512"
- From: Heming Zhao <heming.zhao@xxxxxxxx>
- Re: pvresize will cause a meta-data corruption with error message "Error writing device at 4096 length 512"
- From: Gang He <GHe@xxxxxxxx>
- Re: pvresize will cause a meta-data corruption with error message "Error writing device at 4096 length 512"
- From: David Teigland <teigland@xxxxxxxxxx>
- Re: pvresize will cause a meta-data corruption with error message "Error writing device at 4096 length 512"
- From: Heming Zhao <heming.zhao@xxxxxxxx>
- Re: pvresize will cause a meta-data corruption with error message "Error writing device at 4096 length 512"
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: pvresize will cause a meta-data corruption with error message "Error writing device at 4096 length 512"
- From: Heming Zhao <heming.zhao@xxxxxxxx>
- Re: pvresize will cause a meta-data corruption with error message "Error writing device at 4096 length 512"
- From: Heming Zhao <heming.zhao@xxxxxxxx>
- smartmontools experts roaming around? - multipath
- From: lejeczek <peljasz@xxxxxxxxxxx>
- Re: recovery of a VG - how?
- From: David Teigland <teigland@xxxxxxxxxx>
- recovery of a VG - how?
- From: lejeczek <peljasz@xxxxxxxxxxx>
- Delayed startup
- From: Sam Lunt <samueljlunt@xxxxxxxxx>
- Re: vg activation without backup
- From: Max Halldén <max.hallden@xxxxxxx>
- Re: vg activation without backup
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- vg activation without backup
- From: Max Halldén <max.hallden@xxxxxxx>
- questions about dlm: add TCP multihoming/failover support
- From: Gang He <GHe@xxxxxxxx>
- Re: system boot time regression when using lvm2-2.03.05
- From: Martin Wilck <mwilck@xxxxxxx>
- Re: pvresize will cause a meta-data corruption with error message "Error writing device at 4096 length 512"
- From: Gang He <GHe@xxxxxxxx>
- Re: pvresize will cause a meta-data corruption with error message "Error writing device at 4096 length 512"
- From: Ingo Franzki <ifranzki@xxxxxxxxxxxxx>
- Re: pvresize will cause a meta-data corruption with error message "Error writing device at 4096 length 512"
- From: Ilia Zykov <mail@xxxxxxxxxxx>
- Re: pvresize will cause a meta-data corruption with error message "Error writing device at 4096 length 512"
- From: Ilia Zykov <mail@xxxxxxx>
- pvresize will cause a meta-data corruption with error message "Error writing device at 4096 length 512"
- From: Gang He <GHe@xxxxxxxx>
- Re: system boot time regression when using lvm2-2.03.05
- From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
- Re: system boot time regression when using lvm2-2.03.05
- From: Martin Wilck <mwilck@xxxxxxx>
- Forcing a specific io scheduler
- From: Gionatan Danti <g.danti@xxxxxxxxxx>
- Re: system boot time regression when using lvm2-2.03.05
- From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
- Re: system boot time regression when using lvm2-2.03.05
- From: David Teigland <teigland@xxxxxxxxxx>
- Re: system boot time regression when using lvm2-2.03.05
- From: Martin Wilck <mwilck@xxxxxxx>
- Re: system boot time regression when using lvm2-2.03.05
- From: David Teigland <teigland@xxxxxxxxxx>
- Re: system boot time regression when using lvm2-2.03.05
- From: Heming Zhao <heming.zhao@xxxxxxxx>
- Re: system boot time regression when using lvm2-2.03.05
- From: David Teigland <teigland@xxxxxxxxxx>
- Re: system boot time regression when using lvm2-2.03.05
- From: David Teigland <teigland@xxxxxxxxxx>
- Re: system boot time regression when using lvm2-2.03.05
- From: David Teigland <teigland@xxxxxxxxxx>
- Re: system boot time regression when using lvm2-2.03.05
- From: Heming Zhao <heming.zhao@xxxxxxxx>
- Re: system boot time regression when using lvm2-2.03.05
- From: Martin Wilck <mwilck@xxxxxxx>
- Re: system boot time regression when using lvm2-2.03.05
- From: Heming Zhao <heming.zhao@xxxxxxxx>
- Re: system boot time regression when using lvm2-2.03.05
- From: Heming Zhao <heming.zhao@xxxxxxxx>
- Re: system boot time regression when using lvm2-2.03.05
- From: David Teigland <teigland@xxxxxxxxxx>
- Re: system boot time regression when using lvm2-2.03.05
- From: Heming Zhao <heming.zhao@xxxxxxxx>
- Re: system boot time regression when using lvm2-2.03.05
- From: Heming Zhao <heming.zhao@xxxxxxxx>
- Re: system boot time regression when using lvm2-2.03.05
- From: David Teigland <teigland@xxxxxxxxxx>
- Re: system boot time regression when using lvm2-2.03.05
- From: Heming Zhao <heming.zhao@xxxxxxxx>
- Re: system boot time regression when using lvm2-2.03.05
- From: David Teigland <teigland@xxxxxxxxxx>
- system boot time regression when using lvm2-2.03.05
- From: Heming Zhao <heming.zhao@xxxxxxxx>
- Re: repair pool with bad checksum in superblock
- From: "Dave Cohen" <linux-lvm@xxxxxxxxxxxxxx>
- Re: repair pool with bad checksum in superblock
- From: "Stuart D. Gathman" <stuart@xxxxxxxxxxx>
- Re: repair pool with bad checksum in superblock
- From: "Dave Cohen" <linux-lvm@xxxxxxxxxxxxxx>
- Re: repair pool with bad checksum in superblock
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: repair pool with bad checksum in superblock
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: repair pool with bad checksum in superblock
- From: Gionatan Danti <g.danti@xxxxxxxxxx>
- Re: Programming interface
- From: Christoph Pleger <christoph.pleger@xxxxxxxxxxxxxxxxxx>
- repair pool with bad checksum in superblock
- From: "Dave Cohen" <linux-lvm@xxxxxxxxxxxxxx>
- Re: Programming interface
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: Programming interface
- From: Christoph Pleger <christoph.pleger@xxxxxxxxxxxxxxxxxx>
- Re: Programming interface
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Programming interface
- From: Christoph Pleger <christoph.pleger@xxxxxxxxxxxxxxxxxx>
- Re: dmsetup says "Device does not exist", though it exists
- From: Christoph Pleger <christoph.pleger@xxxxxxxxxxxxxxxxxx>
- Re: dmsetup says "Device does not exist", though it exists
- From: Christoph Pleger <christoph.pleger@xxxxxxxxxxxxxxxxxx>
- Re: dmsetup says "Device does not exist", though it exists
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: dmsetup says "Device does not exist", though it exists
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: dmsetup says "Device does not exist", though it exists
- From: Bernd Eckenfels <ecki@xxxxxxxxxxxxxxxxx>
- Re: dmsetup says "Device does not exist", though it exists
- From: Christoph Pleger <christoph.pleger@xxxxxxxxxxxxxxxxxx>
- Re: dmsetup says "Device does not exist", though it exists
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- dmsetup says "Device does not exist", though it exists
- From: Christoph Pleger <christoph.pleger@xxxxxxxxxxxxxxxxxx>
- Re: Snapshot of RAID 6 Volume
- From: Adam Puleo <adam.puleo@xxxxxxxxxx>
- Re: dlm userspace tool source tarball name format has been changed to dlm-dlm-4.0.x.tar.gz
- From: David Teigland <teigland@xxxxxxxxxx>
- LVM complains about /etc/lvm/cache/.cache it created
- From: Thomas Deutschmann <whissi@xxxxxxxxxx>
- Re: dlm userspace tool source tarball name format has been changed to dlm-dlm-4.0.x.tar.gz
- From: Gang He <GHe@xxxxxxxx>
- LVM complains about /etc/lvm/cache/.cache it created
- From: Thomas Deutschmann <whissi@xxxxxxxxxx>
- Re: dlm userspace tool source tarball name format has been changed to dlm-dlm-4.0.x.tar.gz
- From: David Teigland <teigland@xxxxxxxxxx>
- dlm userspace tool source tarball name format has been changed to dlm-dlm-4.0.x.tar.gz
- From: Gang He <GHe@xxxxxxxx>
- Re: [PATCH] Detect systemd at run-time in 69-dm-lvm-metad.rules
- From: Julian Andres Klode <julian.klode@xxxxxxxxxxxxx>
- Re: [PATCH] Detect systemd at run-time in 69-dm-lvm-metad.rules
- From: Julian Andres Klode <julian.klode@xxxxxxxxxxxxx>
- System hangs after snapshot autoextend, 'dmsetup info' confirms device is SUSPENDED
- From: Tom Crane <TPClvm@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] Detect systemd at run-time in 69-dm-lvm-metad.rules
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: [PATCH] Detect systemd at run-time in 69-dm-lvm-metad.rules
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: [PATCH] Detect systemd at run-time in 69-dm-lvm-metad.rules
- From: Gionatan Danti <g.danti@xxxxxxxxxx>
- Re: [PATCH] Detect systemd at run-time in 69-dm-lvm-metad.rules
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: [PATCH] Detect systemd at run-time in 69-dm-lvm-metad.rules
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: [PATCH] Detect systemd at run-time in 69-dm-lvm-metad.rules
- From: Julian Andres Klode <julian.klode@xxxxxxxxxxxxx>
- Re: [PATCH] Detect systemd at run-time in 69-dm-lvm-metad.rules
- From: Julian Andres Klode <julian.klode@xxxxxxxxxxxxx>
- Re: [PATCH] Detect systemd at run-time in 69-dm-lvm-metad.rules
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: [PATCH] Detect systemd at run-time in 69-dm-lvm-metad.rules
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Recovering Failed LVM Raid-5 Array
- From: Max Ehrlich <max.ehr@xxxxxxxxx>
- [PATCH] Detect systemd at run-time in 69-dm-lvm-metad.rules
- From: Julian Andres Klode <jak@xxxxxxxxxxxxx>
- Re: Which lvm2 code branches are important?
- From: Marian Csontos <mcsontos@xxxxxxxxxx>
- Re: lvdisplay "open" field computing
- From: Simon ELBAZ <selbaz@xxxxxxxxxxxx>
- Re: lvdisplay "open" field computing
- From: Simon ELBAZ <selbaz@xxxxxxxxxxxx>
- Re: lvdisplay "open" field computing
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: lvdisplay "open" field computing
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: lvdisplay "open" field computing
- From: Simon ELBAZ <selbaz@xxxxxxxxxxxx>
- Re: lvdisplay "open" field computing
- From: Simon ELBAZ <selbaz@xxxxxxxxxxxx>
- Re: lvdisplay "open" field computing
- From: Simon ELBAZ <selbaz@xxxxxxxxxxxx>
- Re: lvdisplay "open" field computing
- From: Simon ELBAZ <selbaz@xxxxxxxxxxxx>
- Re: Which lvm2 code branches are important?
- From: Gang He <GHe@xxxxxxxx>
- Re: lvdisplay "open" field computing
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: Which lvm2 code branches are important?
- From: Marian Csontos <mcsontos@xxxxxxxxxx>
- Re: lvdisplay "open" field computing
- From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
- Re: lvdisplay "open" field computing
- From: Simon ELBAZ <selbaz@xxxxxxxxxxxx>
- Re: lvdisplay "open" field computing
- From: Simon ELBAZ <selbaz@xxxxxxxxxxxx>
- Which lvm2 code branches are important?
- From: Gang He <GHe@xxxxxxxx>
- Re: "Unknown feature in status" message when running lvs/lvdisplay against cached LVs
- From: Gang He <GHe@xxxxxxxx>
- Re: lvdisplay "open" field computing
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: lvdisplay "open" field computing
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- lvdisplay "open" field computing
- From: Simon ELBAZ <selbaz@xxxxxxxxxxxx>
- Re: "Unknown feature in status" message when running lvs/lvdisplay against cached LVs
- From: Marian Csontos <mcsontos@xxxxxxxxxx>
- Re: Lvm RAID0 vs lvm striping
- From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
- "Unknown feature in status" message when running lvs/lvdisplay against cached LVs
- From: Gang He <GHe@xxxxxxxx>
- lvmcache shutdown for root filesystem
- From: Paul Richards <paul.richards@xxxxxxxxx>
- Snapshot of RAID 6 Volume
- From: Adam Puleo <adam.puleo@xxxxxxxxxx>
- lvmcache writeback mode and small writes
- From: Paul Richards <paul.richards@xxxxxxxxx>
- Re: Lvm RAID0 vs lvm striping
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
- Lvm RAID0 vs lvm striping
- From: John Ratliff <jdratlif@xxxxxxxxxxxxxxxx>
- Re: Can't remove the snap LV of root volume on multipath disk PV
- From: Gang He <GHe@xxxxxxxx>
- Re: Can't remove the snap LV of root volume on multipath disk PV
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: Question on vgconvert
- From: "Steve Keller" <keller.steve@xxxxxx>
- Can't remove the snap LV of root volume on multipath disk PV
- From: Gang He <GHe@xxxxxxxx>
- Re: confused with lvm2 filter rules
- From: Heming Zhao <heming.zhao@xxxxxxxx>
- Re: confused with lvm2 filter rules
- From: Heming Zhao <heming.zhao@xxxxxxxx>
- Re: confused with lvm2 filter rules
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: confused with lvm2 filter rules
- From: Martin Wilck <mwilck@xxxxxxxx>
- Re: lvm snapshot cannot be removed with the error "Failed to refresh without snapshot"
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: lvm snapshot cannot be removed with the error "Failed to refresh without snapshot"
- From: "Gang He" <ghe@xxxxxxxx>
- lvm snapshot cannot be removed with the error "Failed to refresh without snapshot"
- From: "Gang He" <ghe@xxxxxxxx>
- Re: Question about filter behavior on pvcreate /dev/md0
- From: Heming Zhao <heming.zhao@xxxxxxxx>
- Re: Maximum address used by a virtual disk on a thin pool.
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: Question about filter behavior on pvcreate /dev/md0
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: Maximum address used by a virtual disk on a thin pool.
- From: Gionatan Danti <g.danti@xxxxxxxxxx>
- Maximum address used by a virtual disk on a thin pool.
- From: Ilia Zykov <mail@xxxxxxx>
- Question about filter behavior on pvcreate /dev/md0
- From: Heming Zhao <heming.zhao@xxxxxxxx>
- Re: Question on vgconvert
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Question on vgconvert
- From: "Steve Keller" <keller.steve@xxxxxx>
- LVM cache gets marked as dirty on reboot
- From: Lucas Vinicius Hartmann <lucas.hartmann@xxxxxxxxx>
- Re: [PATCH] Documentation/dm-init: fix multi device example
- From: Jonathan Corbet <corbet@xxxxxxx>
- Re: confused with lvm2 filter rules
- From: Heming Zhao <heming.zhao@xxxxxxxx>
- Re: confused with lvm2 filter rules
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: confused with lvm2 filter rules
- From: Heming Zhao <heming.zhao@xxxxxxxx>
- Re: confused with lvm2 filter rules
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: confused with lvm2 filter rules
- From: Heming Zhao <heming.zhao@xxxxxxxx>
- Re: confused with lvm2 filter rules
- From: Heming Zhao <heming.zhao@xxxxxxxx>
- Re: [PATCH v12] dm: add support to directly boot to a mapped device
- From: Ezequiel Garcia <ezequiel@xxxxxxxxxxxxx>
- Re: [PATCH v12] dm: add support to directly boot to a mapped device
- From: Helen Koike <helen.koike@xxxxxxxxxxxxx>
- Re: [PATCH v12] dm: add support to directly boot to a mapped device
- From: Stephen Boyd <swboyd@xxxxxxxxxxxx>
- Re: confused with lvm2 filter rules
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: [PATCH] Documentation/dm-init: fix multi device example
- From: Stephen Boyd <swboyd@xxxxxxxxxxxx>
- Re: Fast thin volume preallocation?
- From: Ilia Zykov <mail@xxxxxxxxxxx>
- Re: Fast thin volume preallocation?
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: [dm-devel] [PATCH v12] dm: add support to directly boot to a mapped device
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: [PATCH v12] dm: add support to directly boot to a mapped device
- From: Stephen Boyd <swboyd@xxxxxxxxxxxx>
- [PATCH] Documentation/dm-init: fix multi device example
- From: Helen Koike <helen.koike@xxxxxxxxxxxxx>
- Re: confused with lvm2 filter rules
- From: Heming Zhao <heming.zhao@xxxxxxxx>
- Re: Fast thin volume preallocation?
- From: Ilia Zykov <mail@xxxxxxx>
- Re: Fast thin volume preallocation?
- From: Gionatan Danti <g.danti@xxxxxxxxxx>
- Re: A couple of questions on locking library
- From: David Teigland <teigland@xxxxxxxxxx>
- confused with lvm2 filter rules
- From: Heming Zhao <heming.zhao@xxxxxxxx>
- Re: Fast thin volume preallocation?
- From: Joe Thornber <thornber@xxxxxxxxxx>
- Re: A couple of questions on locking library
- From: Shawn Guo <shawnguo@xxxxxxxxxx>
- Re: A couple of questions on locking library
- From: David Teigland <teigland@xxxxxxxxxx>
- Fast thin volume preallocation?
- From: Gionatan Danti <g.danti@xxxxxxxxxx>
- Re: A couple of questions on locking library
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- A couple of questions on locking library
- From: Shawn Guo <shawn.gsc@xxxxxxxxx>
- Local Cache on CLVM
- From: Indivar Nair <indivar.nair@xxxxxxxxxxxx>
- Re: "lvconvert --mirrors 1 --stripes 3 vgtest/lvtest" command succeeds, but no stripes
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- "lvconvert --mirrors 1 --stripes 3 vgtest/lvtest" command succeeds, but no stripes
- From: "Gang He" <ghe@xxxxxxxx>
- Re: recover volume group & locical volumes from PV?
- From: Rainer Fügenstein <rfu@xxxxxxxxxx>
- Re: Does LVM2 support building with LTO enablement?
- From: "Gang He" <ghe@xxxxxxxx>
- Re: Does LVM2 support building with LTO enablement?
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: Does LVM2 support building with LTO enablement?
- From: "Gang He" <ghe@xxxxxxxx>
- Re: LVM and HSM?
- From: Gionatan Danti <g.danti@xxxxxxxxxx>
- Re: recover volume group & locical volumes from PV?
- From: Rainer Fügenstein <rfu@xxxxxxxxxx>
- Re: recover volume group & locical volumes from PV?
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: LVM and HSM?
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: recover volume group & locical volumes from PV?
- From: Roger Heflin <rogerheflin@xxxxxxxxx>
- recover volume group & locical volumes from PV?
- From: "Rainer Fügenstein" <rfu@xxxxxxxxxx>
- LVM and HSM?
- From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
- Does LVM2 support building with LTO enablement?
- From: "Gang He" <ghe@xxxxxxxx>
- Re: pvscan: /dev/sdc: open failed: No medium found
- From: "Gang He" <ghe@xxxxxxxx>
- Re: pvscan: /dev/sdc: open failed: No medium found
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: Internal error: Referenced LV pvmove0 not listed in VG
- From: Anssi Hannula <anssi.hannula@xxxxxx>
- Re: Internal error: Referenced LV pvmove0 not listed in VG
- From: David Teigland <teigland@xxxxxxxxxx>
- Re: Internal error: Referenced LV pvmove0 not listed in VG
- From: Anssi Hannula <anssi.hannula@xxxxxx>
- Re: pvscan: /dev/sdc: open failed: No medium found
- From: David Teigland <teigland@xxxxxxxxxx>
- Re: pvscan: /dev/sdc: open failed: No medium found
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: pvscan: /dev/sdc: open failed: No medium found
- From: "Gang He" <ghe@xxxxxxxx>
- Internal error: Referenced LV pvmove0 not listed in VG
- From: Anssi Hannula <anssi.hannula@xxxxxx>
- Re: pvscan: /dev/sdc: open failed: No medium found
- From: Peter Rajnoha <prajnoha@xxxxxxxxxx>
- Re: pvscan: /dev/sdc: open failed: No medium found
- From: David Teigland <teigland@xxxxxxxxxx>
- Re: Network-attached block storage and local SSDs for dm-cache
- From: Konstantin Ryabitsev <konstantin@xxxxxxxxxxxxxxxxxxx>
- Re: Network-attached block storage and local SSDs for dm-cache
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- pvscan: /dev/sdc: open failed: No medium found
- From: "Gang He" <ghe@xxxxxxxx>
- Re: Network-attached block storage and local SSDs for dm-cache
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
- Network-attached block storage and local SSDs for dm-cache
- From: Konstantin Ryabitsev <konstantin@xxxxxxxxxxxxxxxxxxx>
- Re: [lvm-devel] lvcreate hangs forever and udev work timeout
- From: Eric Ren <renzhengeek@xxxxxxxxx>
- Re: lvcreate hangs forever and udev work timeout
- From: Eric Ren <renzhengeek@xxxxxxxxx>
- Re: [lvm-devel] lvcreate hangs forever and udev work timeout
- From: Eric Ren <renzhengeek@xxxxxxxxx>
- Re: can't remove snapshot
- From: "Lentes, Bernd" <bernd.lentes@xxxxxxxxxxxxxxxxxxxxx>
- Re: [lvm-devel] lvcreate hangs forever and udev work timeout
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: lvcreate hangs forever and udev work timeout
- From: Eric Ren <renzhengeek@xxxxxxxxx>
- Re: [lvm-devel] lvcreate hangs forever and udev work timeout
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: lvcreate hangs forever and udev work timeout
- From: Eric Ren <renzhengeek@xxxxxxxxx>
- Re: lvcreate hangs forever and udev work timeout
- From: Eric Ren <renzhengeek@xxxxxxxxx>
- Re: Aborting. LV mythinpool_tmeta is now incomplete
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: lvcreate hangs forever and udev work timeout
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: [lvm-devel] Aborting. LV mythinpool_tmeta is now incomplete
- From: Eric Ren <renzhengeek@xxxxxxxxx>
- Re: [lvm-devel] Aborting. LV mythinpool_tmeta is now incomplete
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: Aborting. LV mythinpool_tmeta is now incomplete
- From: Eric Ren <renzhengeek@xxxxxxxxx>
- lvcreate hangs forever and udev work timeout
- From: Eric Ren <renzhengeek@xxxxxxxxx>
- Re: can't remove snapshot
- From: "Lentes, Bernd" <bernd.lentes@xxxxxxxxxxxxxxxxxxxxx>
- Re: can't remove snapshot
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: can't remove snapshot
- From: "Lentes, Bernd" <bernd.lentes@xxxxxxxxxxxxxxxxxxxxx>
- Re: Aborting. LV mythinpool_tmeta is now incomplete
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: Aborting. LV mythinpool_tmeta is now incomplete
- From: Eric Ren <renzhengeek@xxxxxxxxx>
- Re: can't remove snapshot
- From: "Lentes, Bernd" <bernd.lentes@xxxxxxxxxxxxxxxxxxxxx>
- Re: Aborting. LV mythinpool_tmeta is now incomplete
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: Aborting. LV mythinpool_tmeta is now incomplete
- From: Eric Ren <renzhengeek@xxxxxxxxx>
- Re: Aborting. LV mythinpool_tmeta is now incomplete
- From: Eric Ren <renzhengeek@xxxxxxxxx>
- Re: Aborting. LV mythinpool_tmeta is now incomplete
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: [lvm-devel] Aborting. LV mythinpool_tmeta is now incomplete
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: can't remove snapshot
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: Aborting. LV mythinpool_tmeta is now incomplete
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: Aborting. LV mythinpool_tmeta is now incomplete
- From: Eric Ren <renzhengeek@xxxxxxxxx>
- Aborting. LV mythinpool_tmeta is now incomplete
- From: Eric Ren <renzhengeek@xxxxxxxxx>
- Re: can't remove snapshot
- From: "Lentes, Bernd" <bernd.lentes@xxxxxxxxxxxxxxxxxxxxx>
- Re: can't remove snapshot
- From: "Lentes, Bernd" <bernd.lentes@xxxxxxxxxxxxxxxxxxxxx>
- Re: can't remove snapshot
- From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
- can't remove snapshot
- From: "Lentes, Bernd" <bernd.lentes@xxxxxxxxxxxxxxxxxxxxx>
- Re: LVM RAID10 busy 100%
- From: "John Stoffel" <john@xxxxxxxxxxx>
- Re: buffer overflow detected: lvcreate terminated
- From: Eric Ren <renzhengeek@xxxxxxxxx>
- Re: LVM RAID10 busy 100%
- From: Andrew Luke Nesbit <email@xxxxxxxxxxxxxxxx>
- buffer overflow detected: lvcreate terminated
- From: Eric Ren <renzhengeek@xxxxxxxxx>
- Re: LVM RAID10 busy 100%
- From: "John Stoffel" <john@xxxxxxxxxxx>
- LVM RAID10 busy 100%
- From: Viacheslav Dubrovskyi <dubrsl@xxxxxxxxx>
- Re: Power loss consistency for RAID
- From: "Stuart D. Gathman" <stuart@xxxxxxxxxxxxxxx>
- Re: Power loss consistency for RAID
- From: Roberto Fastec <roberto.fastec@xxxxxxxxx>
- Re: Power loss consistency for RAID
- From: Roberto Fastec <roberto.fastec@xxxxxxxxx>
- Power loss consistency for RAID
- From: Zheng Lv <lv.zheng.2015@xxxxxxxxx>
- Re: Filesystem corruption with LVM's pvmove onto a PV with a larger physical block size
- From: Nir Soffer <nsoffer@xxxxxxxxxx>
- Re: Filesystem corruption with LVM's pvmove onto a PV with a larger physical block size
- From: Nir Soffer <nsoffer@xxxxxxxxxx>
- Re: LVM thin provisioning on encrypted root unreliable
- From: kurcze <wannabeachicken@xxxxxxxxx>
- Re: Filesystem corruption with LVM's pvmove onto a PV with a larger physical block size
- From: "Stuart D. Gathman" <stuart@xxxxxxxxxxx>
- Re: Filesystem corruption with LVM's pvmove onto a PV with a larger physical block size
- From: David Teigland <teigland@xxxxxxxxxx>
- Re: Filesystem corruption with LVM's pvmove onto a PV with a larger physical block size
- From: Ingo Franzki <ifranzki@xxxxxxxxxxxxx>
- Re: Filesystem corruption with LVM's pvmove onto a PV with a larger physical block size
- From: Ilia Zykov <mail@xxxxxxx>
- Re: Filesystem corruption with LVM's pvmove onto a PV with a larger physical block size
- From: Ingo Franzki <ifranzki@xxxxxxxxxxxxx>
- Re: Filesystem corruption with LVM's pvmove onto a PV with a larger physical block size
- From: Ingo Franzki <ifranzki@xxxxxxxxxxxxx>
- Re: Filesystem corruption with LVM's pvmove onto a PV with a larger physical block size
- From: "Stuart D. Gathman" <stuart@xxxxxxxxxxx>
- Re: Filesystem corruption with LVM's pvmove onto a PV with a larger physical block size
- From: Cesare Leonardi <celeonar@xxxxxxxxx>
- Re: Filesystem corruption with LVM's pvmove onto a PV with a larger physical block size
- From: Cesare Leonardi <celeonar@xxxxxxxxx>
- Re: Filesystem corruption with LVM's pvmove onto a PV with a larger physical block size
- From: Ingo Franzki <ifranzki@xxxxxxxxxxxxx>
- Re: Filesystem corruption with LVM's pvmove onto a PV with a larger physical block size
- From: Nir Soffer <nsoffer@xxxxxxxxxx>
- Re: Filesystem corruption with LVM's pvmove onto a PV with a larger physical block size
- From: Ilia Zykov <mail@xxxxxxxxxxx>
- Re: Filesystem corruption with LVM's pvmove onto a PVwith a larger physical block size
- From: Bernd Eckenfels <ecki@xxxxxxxxxxxxxxxxx>
- Re: Filesystem corruption with LVM's pvmove onto a PV with a larger physical block size
- From: L A Walsh <lvm@xxxxxxxxx>
- Re: Filesystem corruption with LVM's pvmove onto a PV with a larger physical block size
- From: Cesare Leonardi <celeonar@xxxxxxxxx>
- Re: Filesystem corruption with LVM's pvmove onto a PV with a larger physical block size
- From: Ingo Franzki <ifranzki@xxxxxxxxxxxxx>
- Re: Filesystem corruption with LVM's pvmove onto a PVwith a larger physical block size
- From: Ingo Franzki <ifranzki@xxxxxxxxxxxxx>
- Re: Filesystem corruption with LVM's pvmove onto a PV with a larger physical block size
- From: Ingo Franzki <ifranzki@xxxxxxxxxxxxx>
- Re: LVM thin provisioning on encrypted root unreliable
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
- Re: Filesystem corruption with LVM's pvmove onto a PV with a larger physical block size
- From: "Stuart D. Gathman" <stuart@xxxxxxxxxxx>
- Re: Filesystem corruption with LVM's pvmove onto a PV with a larger physical block size
- From: Cesare Leonardi <celeonar@xxxxxxxxx>
- LVM thin provisioning on encrypted root unreliable
- From: kurcze <wannabeachicken@xxxxxxxxx>
- Re: Filesystem corruption with LVM's pvmove onto a PV with a larger physical block size
- From: Ilia Zykov <mail@xxxxxxx>
- Re: Filesystem corruption with LVM's pvmove onto a PV with a larger physical block size
- From: Ingo Franzki <ifranzki@xxxxxxxxxxxxx>
- Re: Filesystem corruption with LVM's pvmove onto a PV with a larger physical block size
- From: Ilia Zykov <mail@xxxxxxx>
- Re: Filesystem corruption with LVM's pvmove onto a PV with a larger physical block size
- From: Ilia Zykov <mail@xxxxxxx>
- Re: Filesystem corruption with LVM's pvmove onto a PV with a larger physical block size
- From: Ilia Zykov <mail@xxxxxxx>
- Re: Filesystem corruption with LVM's pvmove onto a PV with a larger physical block size
- From: Ingo Franzki <ifranzki@xxxxxxxxxxxxx>
- Re: Filesystem corruption with LVM's pvmove onto a PV with a larger physical block size
- From: Ilia Zykov <mail@xxxxxxx>
- Re: Filesystem corruption with LVM's pvmove onto a PV with a larger physical block size
- From: Ingo Franzki <ifranzki@xxxxxxxxxxxxx>
- Re: Filesystem corruption with LVM's pvmove onto a PV with a larger physical block size
- From: "Stuart D. Gathman" <stuart@xxxxxxxxxxx>
- Re: Filesystem corruption with LVM's pvmove onto a PV with a larger physical block size
- From: Cesare Leonardi <celeonar@xxxxxxxxx>
- Re: Filesystem corruption with LVM's pvmove onto a PV with a larger physical block size
- From: Ingo Franzki <ifranzki@xxxxxxxxxxxxx>
- Re: Filesystem corruption with LVM's pvmove onto a PV with a larger physical block size
- From: "Stuart D. Gathman" <stuart@xxxxxxxxxxx>
- Re: Filesystem corruption with LVM's pvmove onto a PV with a larger physical block size
- From: Ingo Franzki <ifranzki@xxxxxxxxxxxxx>
- Re: Filesystem corruption with LVM's pvmove onto a PV with a larger physical block size
- From: Cesare Leonardi <celeonar@xxxxxxxxx>
- Filesystem corruption with LVM's pvmove onto a PV with a larger physical block size
- From: Ingo Franzki <ifranzki@xxxxxxxxxxxxx>
- Re: [PATCH v11] dm: add support to directly boot to a mapped device
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
- Re: [PATCH v12] dm: add support to directly boot to a mapped device
- From: Kees Cook <keescook@xxxxxxxxxxxx>
- [PATCH v12] dm: add support to directly boot to a mapped device
- From: Helen Koike <helen.koike@xxxxxxxxxxxxx>
- Re: [PATCH v11] dm: add support to directly boot to a mapped device
- From: Kees Cook <keescook@xxxxxxxxxxxx>
- [PATCH v11] dm: add support to directly boot to a mapped device
- From: Helen Koike <helen.koike@xxxxxxxxxxxxx>
- Re: Unknown PV missing ?
- From: Roger Heflin <rogerheflin@xxxxxxxxx>
- Re: Mixing devices with different logical or physical block size in oVirt LVM based storage
- From: Vojtech Juranek <vjuranek@xxxxxxxxxx>
- Re: [systemd-devel] Possible race condition with LVM activation during boot
- From: Martin Wilck <mwilck@xxxxxxx>
- Re: [systemd-devel] Possible race condition with LVM activation during boot
- From: suscricions@xxxxxxxxx
- Re: [systemd-devel] Possible race condition with LVM activation during boot
- From: Peter Rajnoha <prajnoha@xxxxxxxxxx>
- Re: Mixing devices with different logical or physical block size in oVirt LVM based storage
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
- Mixing devices with different logical or physical block size in oVirt LVM based storage
- From: Nir Soffer <nsoffer@xxxxxxxxxx>
- Re: Scrub errors after extending LVM RAID1 mirror [full email]
- From: Steve Dodd <steved424@xxxxxxxxx>
- Re: how to copy a snapshot, or restore snapshot without deleting it
- From: "Davis, Matthew" <Matthew.Davis.2@xxxxxxxxxxxxxxxx>
- Re: how to copy a snapshot, or restore snapshot without deleting it
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: Option devices/dir different from /dev does not work
- From: Peter Rajnoha <prajnoha@xxxxxxxxxx>
- Re: lvextend doesn't sync raid1 LV
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: Option devices/dir different from /dev does not work
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Option devices/dir different from /dev does not work
- From: Andrei Borzenkov <arvidjaar@xxxxxxxxx>
- Re: Question about thin-pool/thin LV with stripes
- From: Eric Ren <renzhengeek@xxxxxxxxx>
- lvextend doesn't sync raid1 LV
- From: "Alexander 'Leo' Bergolth" <leo@xxxxxxxxxxxxxxx>
- Re: Question about thin-pool/thin LV with stripes
- From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
- Re: Question about thin-pool/thin LV with stripes
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: Question about thin-pool/thin LV with stripes
- From: Eric Ren <renzhengeek@xxxxxxxxx>
- Re: Question about thin-pool/thin LV with stripes
- From: Eric Ren <renzhengeek@xxxxxxxxx>
- Question about thin-pool/thin LV with stripes
- From: Eric Ren <renzhengeek@xxxxxxxxx>
- Scrub errors after extending LVM RAID1 mirror
- From: Steve Dodd <steved424@xxxxxxxxx>
- Re: Scrub errors after extending LVM RAID1 mirror [full email]
- From: Steve Dodd <steved424@xxxxxxxxx>
- Re: Unable to un-cache logical volume when chunk size is over 1MiB
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: how to copy a snapshot, or restore snapshot without deleting it
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: how to copy a snapshot, or restore snapshot without deleting it
- From: "Davis, Matthew" <Matthew.Davis.2@xxxxxxxxxxxxxxxx>
- Re: how to copy a snapshot, or restore snapshot without deleting it
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: how to copy a snapshot, or restore snapshot without deleting it
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: how to copy a snapshot, or restore snapshot without deleting it
- From: "Davis, Matthew" <Matthew.Davis.2@xxxxxxxxxxxxxxxx>
- lvmcache and bare mdadm arrays
- From: Eugene Vikhman <ujin981@xxxxxxxxx>
- Re: how to copy a snapshot, or restore snapshot without deleting it
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: how to copy a snapshot, or restore snapshot without deleting it
- From: "Davis, Matthew" <Matthew.Davis.2@xxxxxxxxxxxxxxxx>
- Re: how to copy a snapshot, or restore snapshot without deleting it
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: how to copy a snapshot, or restore snapshot without deleting it
- From: "Davis, Matthew" <Matthew.Davis.2@xxxxxxxxxxxxxxxx>
- Re: how to copy a snapshot, or restore snapshot without deleting it
- From: Sarah Newman <srn@xxxxxxxxx>
- Re: how to copy a snapshot, or restore snapshot without deleting it
- From: Tomas Dalebjörk <tomas.dalebjork@xxxxxxxxx>
- Re: how to copy a snapshot, or restore snapshot without deleting it
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: Is "man lvcreate" for "-Z|--zero" incorrectly worded?
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: how to copy a snapshot, or restore snapshot without deleting it
- From: "Davis, Matthew" <Matthew.Davis.2@xxxxxxxxxxxxxxxx>
- Is "man lvcreate" for "-Z|--zero" incorrectly worded?
- From: james harvey <jamespharvey20@xxxxxxxxx>
- Re: how to copy a snapshot, or restore snapshot without deleting it
- From: Tomas Dalebjörk <tomas.dalebjork@xxxxxxxxx>
- Re: how to copy a snapshot, or restore snapshot without deleting it
- From: Marian Csontos <mcsontos@xxxxxxxxxx>
- Re: systemd generator fails if lvmconfig does not find a value
- From: Peter Rajnoha <prajnoha@xxxxxxxxxx>
- how to copy a snapshot, or restore snapshot without deleting it
- From: "Davis, Matthew" <Matthew.Davis.2@xxxxxxxxxxxxxxxx>
- Re: PV not found
- From: Roger Heflin <rogerheflin@xxxxxxxxx>
- Re: PV not found
- From: Giuseppe Vacanti <giuseppe@xxxxxxxxxxx>
- Re: PV not found
- From: Giuseppe Vacanti <giuseppe@xxxxxxxxxxx>
- lvmetad cannot handle md device with big minor number
- From: "Gang He" <ghe@xxxxxxxx>
- systemd generator fails if lvmconfig does not find a value
- From: Bastian Blank <waldi@xxxxxxxxxx>
- Re: PV not found
- From: Gionatan Danti <g.danti@xxxxxxxxxx>
- Re: PV not found
- From: "John Stoffel" <john@xxxxxxxxxxx>
- PV not found
- From: Giuseppe Vacanti <giuseppe@xxxxxxxxxxx>
- Re: lvmcache writethrough synchronisation at system startup
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: lvmcache writethrough synchronisation at system startup
- From: Marcin Wolcendorf <antymat+redhat@xxxxxxxxxxxxxxx>
- Re: lvmcache writethrough synchronisation at system startup
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- lvmcache writethrough synchronisation at system startup
- From: Marcin Wolcendorf <antymat+redhat@xxxxxxxxxxxxxxx>
- Re: lvm.conf backup section
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: lvm.conf backup section
- From: Far Had <farhadk.it@xxxxxxxxx>
- Re: CoW under the hood
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: lvm.conf backup section
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: lvm.conf backup section
- From: Far Had <farhadk.it@xxxxxxxxx>
- CoW under the hood
- From: Far Had <farhadk.it@xxxxxxxxx>
- Re: bcache as a new i/o layer?
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: bcache as a new i/o layer?
- From: Gionatan Danti <g.danti@xxxxxxxxxx>
- Re: bcache as a new i/o layer?
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- bcache as a new i/o layer?
- From: Gionatan Danti <g.danti@xxxxxxxxxx>
- Re: lvm.conf backup section
- From: Far Had <farhadk.it@xxxxxxxxx>
- Re: lvm.conf backup section
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: lvm.conf backup section
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- lvm.conf backup section
- From: Far Had <farhadk.it@xxxxxxxxx>
- Re: lvextend operation results in suspended volume
- From: Andrew Hall <andyjohnhall@xxxxxxxxx>
- Re: lvextend operation results in suspended volume
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- lvextend operation results in suspended volume
- From: Andrew Hall <andyjohnhall@xxxxxxxxx>
- Re: LVM RAID: task mdX_raid1:221 blocked for more than 120 seconds
- From: Cesare Leonardi <celeonar@xxxxxxxxx>
- Re: LVM RAID: task mdX_raid1:221 blocked for more than 120 seconds
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: LVM RAID: task mdX_raid1:221 blocked for more than 120 seconds
- From: Cesare Leonardi <celeonar@xxxxxxxxx>
- Re: LVM RAID: task mdX_raid1:221 blocked for more than 120 seconds
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- LVM RAID: task mdX_raid1:221 blocked for more than 120 seconds
- From: Cesare Leonardi <celeonar@xxxxxxxxx>
- Re: LVM RAID: task mdX_raid1:221 blocked for more than 120 seconds
- From: Jack Wang <jack.wang.usish@xxxxxxxxx>
- LVM RAID: task mdX_raid1:221 blocked for more than 120 seconds
- From: Cesare Leonardi <celeonar@xxxxxxxxx>
- Re: lvm_vg_create_lv_linear() returns error though device was created
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- lvm_vg_create_lv_linear() returns error though device was created
- From: Christoph Pleger <christoph.pleger@xxxxxxxxxxxxxxxxxx>
- Re: lvcreate from a setuid-root binary
- From: matthew patton <pattonme@xxxxxxxxx>
- Re: lvcreate from a setuid-root binary
- From: Christoph Pleger <christoph.pleger@xxxxxxxxxxxxxxxxxx>
- Re: lvcreate from a setuid-root binary
- From: Vladislav Bogdanov <bubble@xxxxxxxxxxxxx>
- Re: lvcreate from a setuid-root binary
- From: Christoph Pleger <christoph.pleger@xxxxxxxxxxxxxxxxxx>
- Re: lvcreate from a setuid-root binary
- From: "Stuart D. Gathman" <stuart@xxxxxxxxxxx>
- Re: lvcreate from a setuid-root binary
- From: matthew patton <pattonme@xxxxxxxxx>
- Re: lvcreate from a setuid-root binary
- From: Christoph Pleger <christoph.pleger@xxxxxxxxxxxxxxxxxx>
- Re: lvcreate from a setuid-root binary
- From: Christoph Pleger <christoph.pleger@xxxxxxxxxxxxxxxxxx>
- Re: lvcreate from a setuid-root binary
- From: Christoph Pleger <christoph.pleger@xxxxxxxxxxxxxxxxxx>
- Re: lvcreate from a setuid-root binary
- From: matthew patton <pattonme@xxxxxxxxx>
- Re: lvcreate from a setuid-root binary
- From: "Bryn M. Reeves" <bmr@xxxxxxxxxx>
- Re: lvcreate from a setuid-root binary
- From: Alasdair G Kergon <agk@xxxxxxxxxx>
- Re: lvcreate from a setuid-root binary
- From: Christoph Pleger <christoph.pleger@xxxxxxxxxxxxxxxxxx>
- Re: lvcreate from a setuid-root binary
- From: Alasdair G Kergon <agk@xxxxxxxxxx>
- Re: lvcreate from a setuid-root binary
- From: Roger Heflin <rogerheflin@xxxxxxxxx>
- Re: lvcreate from a setuid-root binary
- From: Christoph Pleger <christoph.pleger@xxxxxxxxxxxxxxxxxx>
- Re: lvcreate from a setuid-root binary
- From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
- Re: lvcreate from a setuid-root binary
- From: Christoph Pleger <christoph.pleger@xxxxxxxxxxxxxxxxxx>
- Re: lvcreate from a setuid-root binary
- From: Alasdair G Kergon <agk@xxxxxxxxxx>
- lvcreate from a setuid-root binary
- From: Christoph Pleger <christoph.pleger@xxxxxxxxxxxxxxxxxx>
- Re: Detaching a failed cache pool
- From: Liwei <xieliwei@xxxxxxxxx>
- Re: [PATCH v10 0/2] dm: boot a mapped device without an initramfs
- From: Will Drewry <wad@xxxxxxxxxxxx>
- Re: [PATCH v10 0/2] dm: boot a mapped device without an initramfs
- From: Richard Weinberger <richard@xxxxxx>
- [PATCH v10 2/2] init: add support to directly boot to a mapped device
- From: Helen Koike <helen.koike@xxxxxxxxxxxxx>
- [PATCH v10 1/2] dm ioctl: add a device mapper ioctl function.
- From: Helen Koike <helen.koike@xxxxxxxxxxxxx>
- [PATCH v10 0/2] dm: boot a mapped device without an initramfs
- From: Helen Koike <helen.koike@xxxxxxxxxxxxx>
- new releases with important bug fix
- From: David Teigland <teigland@xxxxxxxxxx>
- Re: About --mirrorlog mirrored option in the latest lvm2
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- About --mirrorlog mirrored option in the latest lvm2
- From: "Gang He" <ghe@xxxxxxxx>
- About --mirrorlog mirrored option in the latest lvm2
- From: Gang He <dchg2000@xxxxxxxxx>
- Question about speed of boot with mirror and lvm
- From: Georges Giralt <georges.giralt@xxxxxxx>
- Re: Fails to create LVM volume on the top of RAID1 after upgrade lvm2 to v2.02.180
- From: David Teigland <teigland@xxxxxxxxxx>
- Detaching a failed cache pool
- From: Liwei <xieliwei@xxxxxxxxx>
- Re: Fails to create LVM volume on the top of RAID1 after upgrade lvm2 to v2.02.180
- From: "Gang He" <ghe@xxxxxxxx>
- Re: Fails to create LVM volume on the top of RAID1 after upgrade lvm2 to v2.02.180
- From: David Teigland <teigland@xxxxxxxxxx>
- Re: The node was fenced in the cluster when cmirrord was enabled on LVM2.2.02.120
- From: "Gang He" <ghe@xxxxxxxx>
- Re: Fails to create LVM volume on the top of RAID1 after upgrade lvm2 to v2.02.180
- From: "Gang He" <ghe@xxxxxxxx>
- Re: Why doesn't the lvmcache support the discard (trim) command?
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: [PATCH 0/2] boot to a mapped device
- From: Helen Koike <helen.koike@xxxxxxxxxxxxx>
- Re: Why doesn't the lvmcache support the discard (trim) command?
- From: Gionatan Danti <g.danti@xxxxxxxxxx>
- Re: Why doesn't the lvmcache support the discard (trim) command?
- From: Ilia Zykov <mail@xxxxxxx>
- Re: Why doesn't the lvmcache support the discard (trim) command?
- From: Ilia Zykov <mail@xxxxxxx>
- Re: Why doesn't the lvmcache support the discard (trim) command?
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: Why doesn't the lvmcache support the discard (trim) command?
- From: Gionatan Danti <g.danti@xxxxxxxxxx>
- Re: Why doesn't the lvmcache support the discard (trim) command?
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: Why doesn't the lvmcache support the discard (trim) command?
- From: Ilia Zykov <mail@xxxxxxx>
- Re: Why doesn't the lvmcache support the discard (trim) command?
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: Why doesn't the lvmcache support the discard (trim) command?
- From: Gionatan Danti <g.danti@xxxxxxxxxx>
- The node was fenced in the cluster when cmirrord was enabled on LVM2.2.02.120
- From: "Gang He" <ghe@xxxxxxxx>
- Re: Why doesn't the lvmcache support the discard (trim) command?
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: Fails to create LVM volume on the top of RAID1 after upgrade lvm2 to v2.02.180
- From: "Gang He" <ghe@xxxxxxxx>
- Why doesn't the lvmcache support the discard (trim) command?
- From: Ilia Zykov <linux@xxxxxxx>
- Re: Fails to create LVM volume on the top of RAID1 after upgrade lvm2 to v2.02.180
- From: David Teigland <teigland@xxxxxxxxxx>
- Re: Fails to create LVM volume on the top of RAID1 after upgrade lvm2 to v2.02.180
- From: David Teigland <teigland@xxxxxxxxxx>
- Re: Fails to create LVM volume on the top of RAID1 after upgrade lvm2 to v2.02.180
- From: "Gang He" <ghe@xxxxxxxx>
- Re: Fails to create LVM volume on the top of RAID1 after upgrade lvm2 to v2.02.180
- From: David Teigland <teigland@xxxxxxxxxx>
- Re: Fails to create LVM volume on the top of RAID1 after upgrade lvm2 to v2.02.180
- From: Sven Eschenberg <sven@xxxxxxxxxxxxx>
- Re: Fails to create LVM volume on the top of RAID1 after upgrade lvm2 to v2.02.180
- From: David Teigland <teigland@xxxxxxxxxx>
- Re: [lvm-devel] Can't work normally after attaching disk volumes originally in a VG on another machine
- From: Nir Soffer <nsoffer@xxxxxxxxxx>
- Re: what is the IOPS behavior when partitions of single disk(raid5 backend) are used in an LVM?
- From: Sherpa Sherpa <norbuurgen@xxxxxxxxx>
- Re: what is the IOPS behavior when partitions of single disk(raid5 backend) are used in an LVM?
- From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
- Re: Fails to create LVM volume on the top of RAID1 after upgrade lvm2 to v2.02.180
- From: "Gang He" <ghe@xxxxxxxx>
- Re: Fails to create LVM volume on the top of RAID1 after upgrade lvm2 to v2.02.180
- From: David Teigland <teigland@xxxxxxxxxx>
- Re: WARNING: Combining activation change with other commands is not advised - why?
- From: David Teigland <teigland@xxxxxxxxxx>
- Re: Fails to create LVM volume on the top of RAID1 after upgrade lvm2 to v2.02.180
- From: "Gang He" <ghe@xxxxxxxx>
- Re: what is the IOPS behavior when partitions of single disk(raid5 backend) are used in an LVM?
- From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
- Re: [lvmlockd] lvm command hung with sanlock log "ballot 3 abort1 larger lver in bk..."
- From: David Teigland <teigland@xxxxxxxxxx>
- Re: [lvmlockd] lvm command hung with sanlock log "ballot 3 abort1 larger lver in bk..."
- From: Damon Wang <damon.devops@xxxxxxxxx>
- Re: what is the IOPS behavior when partitions of single disk(raid5 backend) are used in an LVM?
- From: Emmanuel Gelati <emi2fast@xxxxxxxxx>
- Re: [lvmlockd] lvm command hung with sanlock log "ballot 3 abort1 larger lver in bk..."
- From: David Teigland <teigland@xxxxxxxxxx>
- Re: [lvmlockd] lvm command hung with sanlock log "ballot 3 abort1 larger lver in bk..."
- From: David Teigland <teigland@xxxxxxxxxx>
- Re: what is the IOPS behavior when partitions of single disk(raid5 backend) are used in an LVM?
- From: David Teigland <teigland@xxxxxxxxxx>
- Re: [lvmlockd] lvm command hung with sanlock log "ballot 3 abort1 larger lver in bk..."
- From: Damon Wang <damon.devops@xxxxxxxxx>
- what is the IOPS behavior when partitions of single disk(raid5 backend) are used in an LVM?
- From: Sherpa Sherpa <norbuurgen@xxxxxxxxx>
- Re: [lvmlockd] lvm command hung with sanlock log "ballot 3 abort1 larger lver in bk..."
- From: David Teigland <teigland@xxxxxxxxxx>
- Re: [lvmlockd] lvm command hung with sanlock log "ballot 3 abort1 larger lver in bk..."
- From: Damon Wang <damon.devops@xxxxxxxxx>
- Re: [lvmlockd] lvm command hung with sanlock log "ballot 3 abort1 larger lver in bk..."
- From: Damon Wang <damon.devops@xxxxxxxxx>
- [lvmlockd] lvm command hung with sanlock log "ballot 3 abort1 larger lver in bk..."
- From: Damon Wang <damon.devops@xxxxxxxxx>
- Re: Fails to create LVM volume on the top of RAID1 after upgrade lvm2 to v2.02.180
- From: David Teigland <teigland@xxxxxxxxxx>
- Fails to create LVM volume on the top of RAID1 after upgrade lvm2 to v2.02.180
- From: "Gang He" <ghe@xxxxxxxx>
- what is the IOPS behavior when partitions of single disk are used in an LVM?
- From: Sherpa Sherpa <norbuurgen@xxxxxxxxx>
- Re: [lvmlockd] recovery lvmlockd after kill_vg
- From: Damon Wang <damon.devops@xxxxxxxxx>
- Re: [PATCH 0/2] boot to a mapped device
- From: Kees Cook <keescook@xxxxxxxxxxxx>
- Re: snapshot looses origin when other snapshot is merged to the same origin
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
- Re: snapshot looses origin when other snapshot is merged to the same origin
- From: kostrzewa@xxxxxxxxxxxxxx
- Re: [lvmlockd] recovery lvmlockd after kill_vg
- From: Damon Wang <damon.devops@xxxxxxxxx>
- Re: snapshot looses origin when other snapshot is merged to the same origin
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
- Re: [lvmlockd] recovery lvmlockd after kill_vg
- From: David Teigland <teigland@xxxxxxxxxx>
- snapshot looses origin when other snapshot is merged to the same origin
- From: Zbigniew Kostrzewa <kostrzewa@xxxxxxxxxxxxxx>
- Re: [PATCH 0/2] boot to a mapped device
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
- Re: [lvmlockd] recovery lvmlockd after kill_vg
- From: David Teigland <teigland@xxxxxxxxxx>
- Re: [PATCH 0/2] boot to a mapped device
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
- Re: [lvmlockd] recovery lvmlockd after kill_vg
- From: Damon Wang <damon.devops@xxxxxxxxx>
- Fwd: Re: Correct way to remove LVM Snapshot
- From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
- Re: [PATCH 2/2] init: add support to directly boot to a mapped device
- From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
- Re: [PATCH 0/2] boot to a mapped device
- From: Richard Weinberger <richard.weinberger@xxxxxxxxx>
- Re: [PATCH 0/2] boot to a mapped device
- From: Helen Koike <helen.koike@xxxxxxxxxxxxx>
- [PATCH 2/2] init: add support to directly boot to a mapped device
- From: Helen Koike <helen.koike@xxxxxxxxxxxxx>
- [PATCH 1/2] dm ioctl: add a device mapper ioctl function.
- From: Helen Koike <helen.koike@xxxxxxxxxxxxx>
- [PATCH 0/2] boot to a mapped device
- From: Helen Koike <helen.koike@xxxxxxxxxxxxx>
- Correct way to remove LVM Snapshot
- From: Jaco van Niekerk <jaco@xxxxxxxxxxxxx>
- Re: [lvmlockd] recovery lvmlockd after kill_vg
- From: David Teigland <teigland@xxxxxxxxxx>
- [lvmlockd] recovery lvmlockd after kill_vg
- From: Damon Wang <damon.devops@xxxxxxxxx>
- VG metadata and snapshots
- From: Henrik Johansson <henrikj@xxxxxxxxxx>
- Re: Prepend LV
- From: Oleksandr Panchuk <panolex@xxxxxxxxx>
- lvm2: state is not persisted to disk if a snapshot becomes invalid immediately before reboot
- From: "Gang He" <ghe@xxxxxxxx>
- Re: (Why) Does lvmcreate --raid6 need 5 drives?
- From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
- Re: (Why) Does lvmcreate --raid6 need 5 drives?
- From: tudor@xxxxxxxxxxxxxxx
- Re: (Why) Does lvmcreate --raid6 need 5 drives?
- From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
- (Why) Does lvmcreate --raid6 need 5 drives?
- From: tudor@xxxxxxxxxxxxxxx
- Re: Prepend LV
- From: Ondrej Kozina <okozina@xxxxxxxxxx>
- thin POOL metadata
- From: آرش خاوری راد <arash.khavary@xxxxxxxxx>
- Re: Prepend LV
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: Prepend LV
- From: Oleksandr Panchuk <panolex@xxxxxxxxx>
- Re: Prepend LV
- From: Daniel Etter <daniel@xxxxxxxxxxx>
- Re: Volume/Logic group failed to start - Pacemaker
- From: Jaco van Niekerk <jaco@xxxxxxxxxxxxx>
- Prepend LV
- From: Oleksandr Panchuk <panolex@xxxxxxxxx>
- Problem activating lvm-raid
- From: Sven Eschenberg <sven@xxxxxxxxxxxxx>
- Re: Volume/Logic group failed to start - Pacemaker
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Volume/Logic group failed to start - Pacemaker
- From: Jaco van Niekerk <jaco@xxxxxxxxxxxxx>
- Re: Volume/Logic group failed to start - Pacemaker
- From: Jaco van Niekerk <jaco@xxxxxxxxxxxxx>
- Volume/Logic group failed to start - Pacemaker
- From: Jaco van Niekerk <jaco@xxxxxxxxxxxxx>
- corruption on lvconvert --stripes N vg/lv on lv type raid5
- From: Thomas Donnelly <kundarsa@xxxxxxxxx>
- LVM2 commands sometimes were hanged after upgrade to v2.02.180 from v2.02.120
- From: "Gang He" <ghe@xxxxxxxx>
- Re: Version 2.02.179 & 180 & 181 etc. not in git log?
- From: Christian Hesse <list@xxxxxxxx>
- Version 2.02.179 & 180 & 181 etc. not in git log?
- From: Oliver Rath <rath@xxxxxxxx>
- Re: How to upgrade LVM2/CLVM to v2.02.180 from old versions
- From: "Gang He" <ghe@xxxxxxxx>
- Re: How to upgrade LVM2/CLVM to v2.02.180 from old versions
- From: Marian Csontos <mcsontos@xxxxxxxxxx>
- Re: Why use thin_pool_autoextend_threshold < 100 ?
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: How to trash a broke VG
- From: Roger Heflin <rogerheflin@xxxxxxxxx>
- How to upgrade LVM2/CLVM to v2.02.180 from old versions
- From: "Gang He" <ghe@xxxxxxxx>
- How to trash a broke VG
- From: Jeff Allison <jeff.allison@xxxxxxxxxxxxxxx>
- Re: Why use thin_pool_autoextend_threshold < 100 ?
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
- Re: Why use thin_pool_autoextend_threshold < 100 ?
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
- Re: Why use thin_pool_autoextend_threshold < 100 ?
- From: "John Stoffel" <john@xxxxxxxxxxx>
- Re: Why use thin_pool_autoextend_threshold < 100 ?
- From: Marc MERLIN <marc@xxxxxxxxxxx>
- Re: Why use thin_pool_autoextend_threshold < 100 ?
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: Why use thin_pool_autoextend_threshold < 100 ?
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
- Re: Why use thin_pool_autoextend_threshold < 100 ?
- From: Marc MERLIN <marc@xxxxxxxxxxx>
- Re: Why use thin_pool_autoextend_threshold < 100 ?
- From: Marc MERLIN <marc@xxxxxxxxxxx>
- Re: Why use thin_pool_autoextend_threshold < 100 ?
- From: "John Stoffel" <john@xxxxxxxxxxx>
- Re: Why use thin_pool_autoextend_threshold < 100 ?
- From: Marc MERLIN <marc@xxxxxxxxxxx>
- Re: Why use thin_pool_autoextend_threshold < 100 ?
- From: "John Stoffel" <john@xxxxxxxxxxx>
- Re: Can't create thin lv
- From: Marc MERLIN <marc@xxxxxxxxxxx>
- Re: Why use thin_pool_autoextend_threshold < 100 ?
- From: Marc MERLIN <marc@xxxxxxxxxxx>
- Re: Why use thin_pool_autoextend_threshold < 100 ?
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: Can't create thin lv
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Why use thin_pool_autoextend_threshold < 100 ?
- From: Marc MERLIN <marc@xxxxxxxxxxx>
- Re: Can't create thin lv
- From: Marc MERLIN <marc@xxxxxxxxxxx>
- Re: Trying to understand format of LVM2 - Question on Extent Size
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: Can't create thin lv
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: Trying to understand format of LVM2 - Question on Extent Size
- From: "David F." <df7729@xxxxxxxxx>
- Trying to understand format of LVM2 - Question on Extent Size
- From: "David F." <df7729@xxxxxxxxx>
- Re: Can't create thin lv
- From: Marc MERLIN <marc@xxxxxxxxxxx>
- Can't create thin lv
- From: Marc MERLIN <marc@xxxxxxxxxxx>
- Re: Got only half the space of RAID10 LV with 4 PVs (similar to RAID1 cause LV shows it has 4 'Mirrored volumes')
- From: Douglas Paul <doug@xxxxxxxx>
- Re: Unable to un-cache logical volume when chunk size is over 1MiB
- From: Douglas Paul <doug@xxxxxxxx>
- Re: Got only half the space of RAID10 LV with 4 PVs (similar to RAID1 cause LV shows it has 4 'Mirrored volumes')
- From: runappz <runappz@xxxxxxxxx>
- Re: Unable to un-cache logical volume when chunk size is over 1MiB
- From: Ryan Launchbury <ryan@xxxxxxxxxx>
- Re: Got only half the space of RAID10 LV with 4 PVs (similar to RAID1 cause LV shows it has 4 'Mirrored volumes')
- From: Douglas Paul <doug@xxxxxxxx>
- Got only half the space of RAID10 LV with 4 PVs (similar to RAID1 cause LV shows it has 4 'Mirrored volumes')
- From: runappz <runappz@xxxxxxxxx>
- Timeout at shutdown after merging an open snapshot volume
- From: Emond Papegaaij <emond.papegaaij@xxxxxxxxxx>
- Kernel bugcheck on conversion from RAID6 to RAID5
- From: Douglas Paul <doug-lvm@xxxxxxxx>
- Got only half the space of RAID10 LV with 4 PVs (similar to RAID1 cause LV shows it has 4 'Mirrored volumes')
- From: Ben Ma <runappz@xxxxxxxxx>
- vgchange command can not activate mirrored LV in VG
- From: "Gang He" <ghe@xxxxxxxx>
- Re: Recovering from lvm thin metadata exhaustion
- From: Dean Hamstead <dean@xxxxxxxxxxxxxxxxxx>
- Re: Recovering from lvm thin metadata exhaustion
- From: Gionatan Danti <g.danti@xxxxxxxxxx>
- Re: Recovering from lvm thin metadata exhaustion
- From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
- Re: Removing/reinstalling lvmcache
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: [lvmlockd] "VG xxx lock faied: error -221" while lv operation sucess
- From: Damon Wang <damon.devops@xxxxxxxxx>
- Removing/reinstalling lvmcache
- From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
- Re: [lvmlockd] "VG xxx lock faied: error -221" while lv operation sucess
- From: David Teigland <teigland@xxxxxxxxxx>
- Re: Error on RegEx with lv_tags-fields
- From: Peter Rajnoha <prajnoha@xxxxxxxxxx>
- Error on RegEx with lv_tags-fields
- From: Oliver Rath <oliver@xxxxxxxxxxxx>
- Re: Error on RegEx with lv_tags-fields
- From: Damon Wang <damon.devops@xxxxxxxxx>
- Re: [lvmlockd] "VG xxx lock faied: error -221" while lv operation sucess
- From: Damon Wang <damon.devops@xxxxxxxxx>
- Re: [lvmlockd] "VG xxx lock faied: error -221" while lv operation sucess
- From: David Teigland <teigland@xxxxxxxxxx>
- Error on RegEx with lv_tags-fields
- From: Oliver Rath <rath@xxxxxxxx>
- Recovering from lvm thin metadata exhaustion
- From: Dean Hamstead <dean@xxxxxxxxxxxxxxxxxx>
- PE misalignment on USB UAS 512e drives kills performance
- From: "Hector Martin 'marcan'" <marcan@xxxxxxxxx>
- Recovering from lvm thin metadata exhaustion
- From: Dean Hamstead <dean@xxxxxxxxxxxxxxxxxx>
- [SOLVED] Re: Howto set lv_fixed_minor?
- From: Oliver Rath <rath@xxxxxxxx>
- Howto set lv_fixed_minor?
- From: Oliver Rath <rath@xxxxxxxx>
- [lvmlockd] "VG xxx lock faied: error -221" while lv operation sucess
- From: Damon Wang <damon.devops@xxxxxxxxx>
- Re: [lvmlockd] "Duplicate sanlock global locks" warned but not found in "lvmlockctl -i"
- From: Damon Wang <damon.devops@xxxxxxxxx>
- Re: [lvmlockd] "Duplicate sanlock global locks" warned but not found in "lvmlockctl -i"
- From: David Teigland <teigland@xxxxxxxxxx>
- Re: [lvmlockd] "Duplicate sanlock global locks" warned but not found in "lvmlockctl -i"
- From: Damon Wang <damon.devops@xxxxxxxxx>
- Re: [lvmlockd] "Duplicate sanlock global locks" warned but not found in "lvmlockctl -i"
- From: David Teigland <teigland@xxxxxxxxxx>
- [lvmlockd] "Duplicate sanlock global locks" warned but not found in "lvmlockctl -i"
- From: Damon Wang <damon.devops@xxxxxxxxx>
- Re: Unable to un-cache logical volume when chunk size is over 1MiB
- From: Ryan Launchbury <ryan@xxxxxxxxxx>
- Re: Unable to un-cache logical volume when chunk size is over 1MiB
- From: Gionatan Danti <g.danti@xxxxxxxxxx>
- Re: Unable to un-cache logical volume when chunk size is over 1MiB
- From: Gionatan Danti <g.danti@xxxxxxxxxx>
- Re: Unable to un-cache logical volume when chunk size is over 1MiB
- From: Ryan Launchbury <ryan@xxxxxxxxxx>
- Re: Unable to un-cache logical volume when chunk size is over 1MiB
- From: Ryan Launchbury <ryan@xxxxxxxxxx>
- Re: Thin metadata volume bigger than 16GB ?
- From: Gionatan Danti <g.danti@xxxxxxxxxx>
- Re: Unable to un-cache logical volume when chunk size is over 1MiB
- From: Gionatan Danti <g.danti@xxxxxxxxxx>
- Re: Thin metadata volume bigger than 16GB ?
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: Unable to un-cache logical volume when chunk size is over 1MiB
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Re: Unable to un-cache logical volume when chunk size is over 1MiB
- From: Gionatan Danti <g.danti@xxxxxxxxxx>
- Thin metadata volume bigger than 16GB ?
- From: Gionatan Danti <g.danti@xxxxxxxxxx>
- Re: How to get a list of all logical groups or volumes using dbus API
- From: Michael Lipp <mnl@xxxxxx>
- Re: How to get a list of all logical groups or volumes using dbus API
- From: Marian Csontos <mcsontos@xxxxxxxxxx>
- How to get a list of all logical groups or volumes using dbus API
- From: Michael Lipp <mnl@xxxxxx>
- Re: Unable to un-cache logical volume when chunk size is over 1MiB
- From: Ryan Launchbury <ryan@xxxxxxxxxx>
- Re: Unable to un-cache logical volume when chunk size is over 1MiB
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
- Unable to un-cache logical volume when chunk size is over 1MiB
- From: Ryan Launchbury <ryan@xxxxxxxxxx>
- python_lvm_unit.py.in file on v2_02_178 triggered a building error
- From: "Gang He" <ghe@xxxxxxxx>
- Re: Some questions about the upcoming LVM v2_02_178
- From: "Gang He" <ghe@xxxxxxxx>
- Re: Some questions about the upcoming LVM v2_02_178
- From: Joe Thornber <thornber@xxxxxxxxxx>
- Strange behaviour with thinpool and stripes
- From: Oliver Rath <oliver@xxxxxxxxxxxx>
- Re: Some questions about the upcoming LVM v2_02_178
- From: "Gang He" <ghe@xxxxxxxx>
- Re: Some questions about the upcoming LVM v2_02_178
- From: Joe Thornber <thornber@xxxxxxxxxx>
- Some questions about the upcoming LVM v2_02_178
- From: "Gang He" <ghe@xxxxxxxx>
- Re: pvmove does not work at all with version 2.02.177(2)
- From: "Gang He" <ghe@xxxxxxxx>
- Re: pvmove does not work at all with version 2.02.177(2)
- From: Marian Csontos <mcsontos@xxxxxxxxxx>
- Re: pvmove does not work at all with version 2.02.177(2)
- From: "Gang He" <ghe@xxxxxxxx>
- Re: Cannot activate LVs in VG xxx while PVs appear on duplicate devices.
- From: Xen <list@xxxxxxxxxxxxx>
- Cannot activate LVs in VG xxx while PVs appear on duplicate devices.
- From: Wolfgang Denk <wd@xxxxxxx>
[Index of Archives]
[Gluster Users]
[Ceph Users]
[Filesystem Development]
[Kernel Development]
[Security]
[Bugtraq]
[Linux Clusters]
