gmane.linux.lvm.general archive
395 archived articles, newest first (page 4 of 4). Latest articles →
Re: [PATCH 3/6] 11-dm-mpath.rules: use import logic like 13-dm-disk.rules
Fri, 09 Feb 2024 16:38:51 +0100Re: [PATCH 1/6] 11-dm-mpath.rules: don't import properties that are already set
Fri, 09 Feb 2024 16:35:33 +0100Re: [PATCH 6/6] multipathd: don't activate socket activation by default
Thu, 8 Feb 2024 20:05:01 -0500Re: [PATCH 5/6] multipath: udev rules: use configured $(bindir) in udev rules
Thu, 8 Feb 2024 20:04:39 -0500Re: [PATCH 4/6] 11-dm-mpath.rules: handle reloads during coldplug events
Thu, 8 Feb 2024 20:03:54 -0500Re: [PATCH 3/6] 11-dm-mpath.rules: use import logic like 13-dm-disk.rules
Thu, 8 Feb 2024 19:36:10 -0500Re: [PATCH 2/6] 11-dm-mpath.rules: fix list of imported properties
Thu, 8 Feb 2024 19:32:45 -0500Re: [PATCH 1/6] 11-dm-mpath.rules: don't import properties that are already set
Thu, 8 Feb 2024 19:30:45 -0500Re: [PATCH 1/6] 11-dm-mpath.rules: don't import properties that are already set
Tue, 06 Feb 2024 11:50:46 +0100Re: [PATCH 1/6] 11-dm-mpath.rules: don't import properties that are already set
Mon, 5 Feb 2024 15:44:50 -0500[PATCH 6/6] multipathd: don't activate socket activation by default
Mon, 5 Feb 2024 13:46:38 +0100[PATCH 5/6] multipath: udev rules: use configured $(bindir) in udev rules
Mon, 5 Feb 2024 13:46:37 +0100[PATCH 4/6] 11-dm-mpath.rules: handle reloads during coldplug events
Mon, 5 Feb 2024 13:46:36 +0100[PATCH 0/6] multipath-tools: udev rules and service improvements
Mon, 5 Feb 2024 13:46:32 +0100[PATCH 3/6] 11-dm-mpath.rules: use import logic like 13-dm-disk.rules
Mon, 5 Feb 2024 13:46:35 +0100[PATCH 2/6] 11-dm-mpath.rules: fix list of imported properties
Mon, 5 Feb 2024 13:46:34 +0100[PATCH 1/6] 11-dm-mpath.rules: don't import properties that are already set
Mon, 5 Feb 2024 13:46:33 +0100Re: Any way in LVM to deal with 512e vs 4Kn physical devices?
Thu, 25 Jan 2024 20:35:03 -0500Re: Any way in LVM to deal with 512e vs 4Kn physical devices?
Thu, 25 Jan 2024 19:21:55 -0600Re: Any way in LVM to deal with 512e vs 4Kn physical devices?
Thu, 25 Jan 2024 14:05:26 -0500Re: [Question] why not flush device cache at _vg_commit_raw
Thu, 25 Jan 2024 07:17:51 +0800Re: Any way in LVM to deal with 512e vs 4Kn physical devices?
Wed, 24 Jan 2024 15:17:19 -0600Re: Any way in LVM to deal with 512e vs 4Kn physical devices?
Wed, 24 Jan 2024 11:18:36 -0500Re: [Question] why not flush device cache at _vg_commit_raw
Wed, 24 Jan 2024 14:13:17 +0100Re: [Question] why not flush device cache at _vg_commit_raw
Wed, 24 Jan 2024 13:35:49 +0100Re: [Question] why not flush device cache at _vg_commit_raw
Wed, 24 Jan 2024 12:58:45 +0100Re: [Question] why not flush device cache at _vg_commit_raw
Tue, 23 Jan 2024 18:50:01 +0100Re: [Question] why not flush device cache at _vg_commit_raw
Tue, 23 Jan 2024 11:42:26 -0500Re: [Question] why not flush device cache at _vg_commit_raw
Tue, 23 Jan 2024 09:15:32 +0100Re: [Question] why not flush device cache at _vg_commit_raw
Tue, 23 Jan 2024 09:54:54 +0800Re: [Question] why not flush device cache at _vg_commit_raw
Mon, 22 Jan 2024 17:01:52 +0100Re: [Question] why not flush device cache at _vg_commit_raw
Mon, 22 Jan 2024 18:26:20 +0300Re: [Question] why not flush device cache at _vg_commit_raw
Mon, 22 Jan 2024 15:52:57 +0100Re: [Question] why not flush device cache at _vg_commit_raw
Mon, 22 Jan 2024 14:46:13 +0100Re: [Question] why not flush device cache at _vg_commit_raw
Mon, 22 Jan 2024 13:48:41 +0100[Question] why not flush device cache at _vg_commit_raw
Mon, 22 Jan 2024 19:22:09 +0800Re: add volatile flag to PV/LVs (for cache) to avoid degraded state on reboot
Mon, 22 Jan 2024 11:58:47 +0100Re: Any way in LVM to deal with 512e vs 4Kn physical devices?
Sat, 20 Jan 2024 20:56:02 +0000Re: add volatile flag to PV/LVs (for cache) to avoid degraded state on reboot
Sat, 20 Jan 2024 20:29:40 +0000Re: Any way in LVM to deal with 512e vs 4Kn physical devices?
Sat, 20 Jan 2024 13:00:54 -0500Re: Any way in LVM to deal with 512e vs 4Kn physical devices?
Sat, 20 Jan 2024 04:45:35 +0000Re: add volatile flag to PV/LVs (for cache) to avoid degraded state on reboot
Thu, 18 Jan 2024 20:50:06 +0100Re: add volatile flag to PV/LVs (for cache) to avoid degraded state on reboot
Thu, 18 Jan 2024 16:40:47 +0100Re: add volatile flag to PV/LVs (for cache) to avoid degraded state on reboot
Wed, 17 Jan 2024 23:00:08 +0100Re: Any way in LVM to deal with 512e vs 4Kn physical devices?
Wed, 17 Jan 2024 22:05:02 +0300Re: Any way in LVM to deal with 512e vs 4Kn physical devices?
Wed, 17 Jan 2024 09:24:10 -0500Re: Any way in LVM to deal with 512e vs 4Kn physical devices?
Wed, 17 Jan 2024 09:10:15 -0500Re: Any way in LVM to deal with 512e vs 4Kn physical devices?
Wed, 17 Jan 2024 09:06:57 -0500Re: Any way in LVM to deal with 512e vs 4Kn physical devices?
Wed, 17 Jan 2024 06:13:29 -0600Re: Any way in LVM to deal with 512e vs 4Kn physical devices?
Wed, 17 Jan 2024 12:48:32 +0100Re: Any way in LVM to deal with 512e vs 4Kn physical devices?
Wed, 17 Jan 2024 11:21:43 +0000Re: add volatile flag to PV/LVs (for cache) to avoid degraded state on reboot
Wed, 17 Jan 2024 12:08:14 +0100Re: Any way in LVM to deal with 512e vs 4Kn physical devices?
Wed, 17 Jan 2024 11:36:24 +0100Re: Any way in LVM to deal with 512e vs 4Kn physical devices?
Wed, 17 Jan 2024 07:22:14 +0000Re: Any way in LVM to deal with 512e vs 4Kn physical devices?
Tue, 16 Jan 2024 20:17:31 +0000Re: Any way in LVM to deal with 512e vs 4Kn physical devices?
Tue, 16 Jan 2024 20:13:15 +0000Re: Any way in LVM to deal with 512e vs 4Kn physical devices?
Tue, 16 Jan 2024 22:30:36 +0300Re: Any way in LVM to deal with 512e vs 4Kn physical devices?
Tue, 16 Jan 2024 13:24:29 -0500Re: Any way in LVM to deal with 512e vs 4Kn physical devices?
Mon, 15 Jan 2024 15:07:49 -0600Any way in LVM to deal with 512e vs 4Kn physical devices?
Mon, 15 Jan 2024 07:30:51 +0000pvmove stuck/hung
Fri, 12 Jan 2024 19:14:38 -0800add volatile flag to PV/LVs (for cache) to avoid degraded state on reboot
Fri, 12 Jan 2024 18:19:12 +0000pvmove stuck/hung
Mon, 8 Jan 2024 13:59:41 -0800Re: Unable to resize a logical volume due to wrong reported asked size
Fri, 5 Jan 2024 09:17:15 +0100Re: Unable to resize a logical volume due to wrong reported asked size
Thu, 4 Jan 2024 16:00:08 -0600Unable to resize a logical volume due to wrong reported asked size
Thu, 4 Jan 2024 22:01:04 +0100Re: Should issue_discards be enabled when e2scrub is used on an SSD?
Tue, 2 Jan 2024 13:01:35 +0100Re: Should issue_discards be enabled when e2scrub is used on an SSD?
Tue, 2 Jan 2024 12:45:18 +0100Re: Should issue_discards be enabled when e2scrub is used on an SSD?
Tue, 2 Jan 2024 12:13:28 +0100Re: Should issue_discards be enabled when e2scrub is used on an SSD?
Tue, 2 Jan 2024 11:41:05 +0100Should issue_discards be enabled when e2scrub is used on an SSD?
Fri, 29 Dec 2023 01:48:00 +0100Re: lvmcache not promoting blocks when there's free RAM
Wed, 20 Dec 2023 19:28:32 +0100lvm2 2.03.23 git tag
Wed, 20 Dec 2023 17:34:05 +0100Re: lvmcache not promoting blocks when there's free RAM
Wed, 20 Dec 2023 16:42:54 +0100Re: lvmcache not promoting blocks when there's free RAM
Wed, 20 Dec 2023 08:01:47 +0100lvmcache not promoting blocks when there's free RAM
Tue, 19 Dec 2023 23:28:24 +0100Re: vgcreate fails with 'already exists in filesystem' error
Tue, 12 Dec 2023 15:54:37 +0100vgcreate fails with 'already exists in filesystem' error
Mon, 11 Dec 2023 19:10:52 +0530[PATCH] man: add inte(g)rity to man lvs
Wed, 6 Dec 2023 10:26:13 +0100Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
Tue, 21 Nov 2023 20:35:00 +0000Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
Tue, 21 Nov 2023 12:25:50 -0600Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
Tue, 21 Nov 2023 18:10:12 +0000Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
Tue, 21 Nov 2023 11:56:33 -0600Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
Tue, 21 Nov 2023 14:39:11 +0000Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
Mon, 20 Nov 2023 11:13:01 +0100Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
Fri, 17 Nov 2023 21:05:22 +0000Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
Fri, 17 Nov 2023 16:03:12 -0500Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
Fri, 17 Nov 2023 14:16:48 -0600Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
Fri, 17 Nov 2023 14:57:35 -0500Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
Fri, 17 Nov 2023 09:25:50 -0600Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
Thu, 16 Nov 2023 20:47:22 -0500Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
Thu, 16 Nov 2023 15:22:06 -0500Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
Thu, 16 Nov 2023 11:27:00 -0600Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
Thu, 16 Nov 2023 11:13:07 -0600Re: discuss about commit 3b0f9ce: filter-mpath: get wwids from sysfs vpd_pg83
Thu, 16 Nov 2023 10:34:51 -0600
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.