Discuss

discuss@lists.centos.org

34753 discussions

Start a nNew thread

CentOS-announce Digest, Vol 124, Issue 15
by centos-announce-request＠centos.org 27 Jun '15

27 Jun '15

1 0

Re: [CentOS] LVM hatred, was Re: /boot on a separate partition?
by Gordon Messmer 26 Jun '15

26 Jun '15

On 06/26/2015 07:58 AM, Mark Milhollan wrote: > On Wed, 24 Jun 2015, Gordon Messmer wrote: > >> 1) If you have a system with a single disk, you have to reboot to add >> partitions for new guests. Linux won't refresh the partition table on the disk >> it boots from. > I'm not sure this is still true, but I use LVM almost everywhere so I > seldom need to try. It's definitely still true on CentOS 7. >> 3) If you want redundancy, partitions on top of RAID is more complex than LVM >> on top of RAID. As far as I know, partitions on top of RAID are subject to the >> same limitation as in #1. > They look the same to me, and share the same limitations (WRT the PV). Create a RAID1 volume on two drives. Partition that volume. Where is your partition table? Is it in a spot where your BIOS/UEFI or another OS will see it? Will that non-Linux system try to open or modify the partitions inside your RAID? It depends on what metadata version you use. If you set this up in Anaconda, it's going to be version 0.90, and your partition table will be in a spot where a non-Linux system will read it. There's no ambiguity with LVM. That's what I mean when I say that it's less complicated. The format of MBR and GPT partition tables are imposed by the design of BIOS and UEFI. There is no good reason to use them for any purpose other than identifying the location of a filesytem that BIOS or UEFI must be able to read. The limitation I was referring to was that as far as I know, if Linux has mounted filesystems from a partitioned RAID set, you can't modify partitions without rebooting. That limitation doesn't affect LVM. > Either can be partitioned but making more LVs is indeed simpler than > using DM to partition a partition or MD. I'd like to use LVM RAID and > never again have RAIDed partitions, so that I can choose the RAID level > per LV, alas LVM RAID MDs don't appear in /proc/mdstat so monitoring > them is somewhat more annoying. > >> 4) As far as I know, Anaconda can't set up a logical volume that's a redundant >> type, so LVM on top of RAID is the only practical way to support redundant >> storage of your host filesystems. > Anaconda has many deficiencies and indeed I am annoyed enough with it > that I often skip trying to use its new disk manager, but making the PV > on an MD RAID isn't impossible I know, that's what I said was the only practical way to support redundant storage (when using LVM). > , or alternatively making the LVs > redundant after install is a single command (each) and you can choose > whether it should be mere mirroring or some MD manged RAID level (modulo > the LVM RAID MD monitoring issue). I hadn't realized that. That's an interesting alternative to MD RAID, particularly for users who want LVs with different RAID levels.

3 2

Possible bug in kickstart
by James A. Peltier 26 Jun '15

26 Jun '15

Hello All, I seem to have run into a bug with the new --bridgeslaves=<INTERFACE> option. It would seem that if I tell the bridge device to use a virtual interface (like bond0) rather than a physical interface (em1/em2) that kickstart completely barfs on it. I have provided my network section below which works fine as long as i don't enable all the bridge content. When the installation starts off the creation of bond0 and all VLANs on bond0 go without issue. Jumping into TTY2 I can type 'ip a' and see all the bond0 device and bond0.VLANID devices no problem. When I enable bridge content with --bridgeslaves=bond0 or --bridgeslaves=bond0.VLANID anaconda barfs When I enable bridge content with --bridgeslaves=em1 or --bridgeslaves=em2 anaconda doesn't have an issue. Is this expected behaviour? I really don't want to have to manually manipulate the ifcfg-bond* interfaces and create the ifcfg-BRIDGE* interfaces manually so I'd like this to work. # Configure a bond over the slaves in failover mode network --device=bond0 --noipv6 --bootproto=dhcp --onboot=yes --bondslaves=em1,em2 --bondopts=mode=active-backup;primary=em1 --activate # Configure VLANs network --device=bond0 --vlanid=11 --noipv6 --onboot=yes --bootproto=dhcp --activate network --device=bond0 --vlanid=100 --noipv6 --onboot=yes --bootproto=dhcp --activate network --device=bond0 --vlanid=302 --noipv6 --onboot=yes --bootproto=dhcp --activate network --device=bond0 --vlanid=303 --noipv6 --onboot=yes --bootproto=dhcp --activate network --device=bond0 --vlanid=304 --noipv6 --onboot=yes --bootproto=dhcp --activate network --device=bond0 --vlanid=306 --noipv6 --onboot=yes --bootproto=dhcp --activate # Create a bridge on the bonded VLAN interfaces network --device=FASNET --bridgeslaves=bond0 network --device=GLUSTER --bridgeslaves=bond0.11 network --device=EXPERIMENTAL --bridgeslaves=bond0.302 network --device=NAT --bridgeslaves=bond0.303 network --device=DMZ2 --bridgeslaves=bond0.304 network --device=NETM --bridgeslaves=bond0.306 -- James A. Peltier IT Services - Research Computing Group Simon Fraser University - Burnaby Campus Phone : 604-365-6432 Fax : 778-782-3045 E-Mail : jpeltier(a)sfu.ca Website : http://www.sfu.ca/itservices Twitter : @sfu_rcg Powering Engagement Through Technology

1 1

An odd X question
by m.roth＠5-cent.us 26 Jun '15

26 Jun '15

I've got a headless server running CentOS 7. I've got a user who wants to run some graphical software on it, and view using x forwarding. What I don't have clear is how to set this up. I've just installed xorg-x11-server-[Xorg, common]. I assume I need to run X, but I don't see running this in runlevel 5. Thoughts? mark "and why is it called xorg-x11-server, when in X terminology, it's the client?"* * Which I always thought was bass-ackward, but...

7 7

LVM hatred, was Re: /boot on a separate partition?
by Chris Murphy 26 Jun '15

26 Jun '15

Gordon Messmer gordon.messmer at gmail.com Wed Jun 24 01:42:13 UTC 2015 > I wondered the same thing, especially in the context of someone who > prefers virtual machines. LV-backed VMs have *dramatically* better disk > performance than file-backed VMs. I did a bunch of testing of Raw, qcow2, and LV backed VM storage circa Fedora 19/20 and found very little difference. What mattered most was the (libvirt) cache setting, accessible by virsh edit the xml config or virt-manager through the GUI. There have been a lot of optimizations in libvirt and qemu that make qcow2 files perform comparable to LVs. For migrating VMs, it's easier if they're a file. And qcow2 snapshots are more practical than LVM (thick) snapshots. The thin snapshots are quite good though they take a lot of familiarity with setting them up. -- Chris Murphy

3 3

CentOS-announce Digest, Vol 124, Issue 14
by centos-announce-request＠centos.org 26 Jun '15

26 Jun '15

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CESA-2015:1185 Moderate CentOS 6 nss-util Security Update (Johnny Hughes) 2. CESA-2015:1185 Moderate CentOS 6 nss Security Update (Johnny Hughes) 3. CEBA-2015:1180 CentOS 6 kdebase-workspace BugFix Update (Johnny Hughes) 4. CESA-2015:1185 Moderate CentOS 7 nss Security Update (Johnny Hughes) 5. CESA-2015:1185 Moderate CentOS 7 nss-util Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Thu, 25 Jun 2015 10:23:56 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2015:1185 Moderate CentOS 6 nss-util Security Update Message-ID: <20150625102356.GA31889(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2015:1185 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2015-1185.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 07b2323f67221bfa440bcbf79d099b401f0b05539d5c7c6054682eea1a054043 nss-util-3.19.1-1.el6_6.i686.rpm 3a33c0c12ce812e18d86d1ba0601546ba645babb4b129f5318472180ddfb3ccb nss-util-devel-3.19.1-1.el6_6.i686.rpm x86_64: 07b2323f67221bfa440bcbf79d099b401f0b05539d5c7c6054682eea1a054043 nss-util-3.19.1-1.el6_6.i686.rpm 6d18c09300d59c832734701ff7403398a46ef2faa8897ae52f88d204a2d610a2 nss-util-3.19.1-1.el6_6.x86_64.rpm 3a33c0c12ce812e18d86d1ba0601546ba645babb4b129f5318472180ddfb3ccb nss-util-devel-3.19.1-1.el6_6.i686.rpm abceb0b92d73c562720382d69b6e9af3d72f85257fb66dbad9de07652e68e844 nss-util-devel-3.19.1-1.el6_6.x86_64.rpm Source: 8b4f5d17d8260f788fc58e0d22bc4f6d79481822be4218403e3d8dfc7f92229b nss-util-3.19.1-1.el6_6.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 2 Date: Thu, 25 Jun 2015 11:59:06 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2015:1185 Moderate CentOS 6 nss Security Update Message-ID: <20150625115906.GA34166(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2015:1185 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2015-1185.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: a74da22a4f4859a8a476af17f4f871901bb90da15afcf16665a66f0b6c71afdb nss-3.19.1-3.el6_6.i686.rpm 5386cf07a44380ffb202ba7e82f10220d36abc97478b49993b7a95690d085c9d nss-devel-3.19.1-3.el6_6.i686.rpm d3da3f8d93cf5505d4d3c83a1f4cf610ffccf96f6dae68e18d9ec0befea03198 nss-pkcs11-devel-3.19.1-3.el6_6.i686.rpm 66ae3f655a0f04df9a4ab92a744a3754c5634097e305692a71908a2b26e99f85 nss-sysinit-3.19.1-3.el6_6.i686.rpm f95028d6f4dab7cac8b000a6d5edc8ad50b4c51fa9098a11bd1537278c589d65 nss-tools-3.19.1-3.el6_6.i686.rpm x86_64: a74da22a4f4859a8a476af17f4f871901bb90da15afcf16665a66f0b6c71afdb nss-3.19.1-3.el6_6.i686.rpm 527b9685f9466312d5dc12fd5c95a17eaca308b93cb6e6e2b6e90f67b6199839 nss-3.19.1-3.el6_6.x86_64.rpm 5386cf07a44380ffb202ba7e82f10220d36abc97478b49993b7a95690d085c9d nss-devel-3.19.1-3.el6_6.i686.rpm 3e9aad3ff99d1c8dd83246b5182715bcf6b3fa7b3ac8d185aa39808c5365b3eb nss-devel-3.19.1-3.el6_6.x86_64.rpm d3da3f8d93cf5505d4d3c83a1f4cf610ffccf96f6dae68e18d9ec0befea03198 nss-pkcs11-devel-3.19.1-3.el6_6.i686.rpm d43230dd26cd5d746e578f2b8dd45dde8b9db72810bcdc43aa1675c5d8138832 nss-pkcs11-devel-3.19.1-3.el6_6.x86_64.rpm 5544ff6bb87c77715fa11ad9ad61941f57dffdfde8427129c75090ae0f1851da nss-sysinit-3.19.1-3.el6_6.x86_64.rpm d682e4187fda2f1b2222ea70fb7795887bdb7fc6168167fb51fc58bacd87b90c nss-tools-3.19.1-3.el6_6.x86_64.rpm Source: b30fb858dcec5a154713cfd27386aa48def4cf819f2ed39f586c513f8eb1d209 nss-3.19.1-3.el6_6.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 3 Date: Thu, 25 Jun 2015 12:13:57 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2015:1180 CentOS 6 kdebase-workspace BugFix Update Message-ID: <20150625121357.GA51726(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2015:1180 Upstream details at : https://rhn.redhat.com/errata/RHBA-2015-1180.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 3f6d88392299834369f0dc5c4f86baf323417aaa409e5b58daaa86a9c9e68829 kdebase-workspace-4.3.4-30.el6_6.i686.rpm 6347bc4b6155060ae654271f0761cefff84bbc4550b81d335437438145b05b04 kdebase-workspace-akonadi-4.3.4-30.el6_6.i686.rpm 6b0a17dc25a328cde571c9b80a4777a32dcb8874f283f253d1f54e941c6dfd1c kdebase-workspace-devel-4.3.4-30.el6_6.i686.rpm 2b3508584d1a1f79d95e5a2566d59980330f4dfe8a44e7e74b924361b9c48cb1 kdebase-workspace-libs-4.3.4-30.el6_6.i686.rpm f324c331c4c8b169d168ae0b7dd37e77a341df170de9895e51f3c1dc2982a112 kdebase-workspace-python-applet-4.3.4-30.el6_6.i686.rpm 4b6334b13161f3b23ce271d0a4d38129483b8cec77075972e043034915efc4e6 kdebase-workspace-wallpapers-4.3.4-30.el6_6.noarch.rpm 55bfd8daf41d207ae0051b31e2c811b9023fe9d16b0267d1cbbe9040e74a17d2 kdm-4.3.4-30.el6_6.i686.rpm 40bbfe9aa15744d6971811ccd966b695f6b3335316546c80dc2c7f08e1f0d047 ksysguardd-4.3.4-30.el6_6.i686.rpm ebd8ef145e2d1a7c101e02da1f04200d03a6b9e5401fdc43c405f5ac4d256cd4 oxygen-cursor-themes-4.3.4-30.el6_6.noarch.rpm x86_64: 9219e30a29bc81c4b2d31bdcecba7774d75d1909d5162b7312eff8ec99972ddf kdebase-workspace-4.3.4-30.el6_6.x86_64.rpm 7388b4d6818b4914d2a4f812d54820bda72762113f7252e218d7ffc6f4677d25 kdebase-workspace-akonadi-4.3.4-30.el6_6.x86_64.rpm 6b0a17dc25a328cde571c9b80a4777a32dcb8874f283f253d1f54e941c6dfd1c kdebase-workspace-devel-4.3.4-30.el6_6.i686.rpm 04701e7b0f2cb25112540456c8de64d0b2e2c2b0dfbca160d682c6ae9fadaa49 kdebase-workspace-devel-4.3.4-30.el6_6.x86_64.rpm 2b3508584d1a1f79d95e5a2566d59980330f4dfe8a44e7e74b924361b9c48cb1 kdebase-workspace-libs-4.3.4-30.el6_6.i686.rpm d4860b2d83767d6454ca2b8623afe2bfdd00234b570b61b81aa1175ce638cb6c kdebase-workspace-libs-4.3.4-30.el6_6.x86_64.rpm 7a6ba4bcfc2401db8b6a5341327cf5a7d0a11c74c92c25290ba02e1e01d18d0c kdebase-workspace-python-applet-4.3.4-30.el6_6.x86_64.rpm 4b6334b13161f3b23ce271d0a4d38129483b8cec77075972e043034915efc4e6 kdebase-workspace-wallpapers-4.3.4-30.el6_6.noarch.rpm 450da92e9b9bd08a3429e35fda30e98f7dd316083db841b05e47c219a7fb0f8a kdm-4.3.4-30.el6_6.x86_64.rpm 4c04b9b7ea2fe85a69b584f13527aa7b163bf2fe17c64a91ae0959dd2ac3537b ksysguardd-4.3.4-30.el6_6.x86_64.rpm ebd8ef145e2d1a7c101e02da1f04200d03a6b9e5401fdc43c405f5ac4d256cd4 oxygen-cursor-themes-4.3.4-30.el6_6.noarch.rpm Source: 55837600e115f5c886b00b14b2b467e54f42be110365b9acb8f265da0f12a041 kdebase-workspace-4.3.4-30.el6_6.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 4 Date: Thu, 25 Jun 2015 12:14:36 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2015:1185 Moderate CentOS 7 nss Security Update Message-ID: <20150625121436.GA51824(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2015:1185 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2015-1185.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: c36669d51214d57b5a82f9b079c12ff025b33dfdc417376f01ad3538ba44ede2 nss-3.19.1-3.el7_1.i686.rpm 67217f72404c892ec99f3620176a88815865c9e0760cfcde205ccb438c27c936 nss-3.19.1-3.el7_1.x86_64.rpm 796fd60bf87cc31757a284190ef1471ecf6d677c48efc1867b5ca70ed07254bf nss-devel-3.19.1-3.el7_1.i686.rpm 24105b14d55d7fe635d2a61b428f14e6f60f97592ee973e9627cf4a67acfc963 nss-devel-3.19.1-3.el7_1.x86_64.rpm 94d8574d74fdf11669e69adc0c8a9c05ee261feb186bb742cfe6ca76d651454f nss-pkcs11-devel-3.19.1-3.el7_1.i686.rpm 6b020d9acf4a76177c3bba65766a32f486e669da53464ea4b5a33dbc6a119eed nss-pkcs11-devel-3.19.1-3.el7_1.x86_64.rpm 43911fd7e9c230d4ed1f92cf709e150d2a671228256a6abaa99bd2ee541287a8 nss-sysinit-3.19.1-3.el7_1.x86_64.rpm f724e35a7efafae8f3babbb7274adb518c642a098fd087cdc09fab867b7b4a43 nss-tools-3.19.1-3.el7_1.x86_64.rpm Source: 3560838cde182f07528ad9cde1afbd899b3274c50328c21c1ccb521ffa327e29 nss-3.19.1-3.el7_1.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 5 Date: Thu, 25 Jun 2015 12:14:50 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2015:1185 Moderate CentOS 7 nss-util Security Update Message-ID: <20150625121450.GA51893(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2015:1185 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2015-1185.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 2ef5f1ea879e3bb34c930bdcb7ebea42bb1f3a3440e4f8f61b34a9bf042a42eb nss-util-3.19.1-1.el7_1.i686.rpm c379f6530da7996ea4d52370038ff0dde6f69395b4b38bd184f9ea3ff93cd066 nss-util-3.19.1-1.el7_1.x86_64.rpm 420eda8ab708d8b616e19288813a47f6a82f013c58ca474d91d544d4b4fe7951 nss-util-devel-3.19.1-1.el7_1.i686.rpm f4609893801a577d38f7a447775120bcef017207fabab038152ed248d8b262f2 nss-util-devel-3.19.1-1.el7_1.x86_64.rpm Source: 25631048669b631db267364a4adff132c337756e91b3880db2ca5f6cc0e05219 nss-util-3.19.1-1.el7_1.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org http://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 124, Issue 14 ************************************************

1 0

Trying to update a CentOS 7.1 docker image, getting errors on yum update regarding iputils
by Kenneth Wolcott 26 Jun '15

26 Jun '15

Hi All; Is there a corrupt iputils rpm located on one or more of the CentOS update file servers? Here's an excerpt of the output of my yum update -y command: Updating : iputils-20121221-6.el7_1.1.x86_64 17/44Error unpacking rpm package iputils-20121221-6.el7_1.1.x86_64 error: unpacking of archive failed on file /usr/bin/ping: cpio: cap_set_file error: iputils-20121221-6.el7_1.1.x86_64: install failed Advice please. Thanks, Ken Wolcott

2 1

LVM hatred, was Re: /boot on a separate partition?
by Chris Murphy 25 Jun '15

25 Jun '15

Chris Adams linux at cmadams.net Wed Jun 24 19:06:19 UTC 2015 >Btrfs may eventually obsolete a lot of > uses of LVM, but that's down the road. LVM is the emacs of storage. It'll be here forever. Btrfs doesn't export (virtual) block devices like LVM can, so it can't be a backing for say iSCSI. And it's also at the moment rather catatonic when it comes to VM images. This is mitigated if you set xattr +C at image create time (it must be zero length file for +C to take). But if you cp --reflink or snapshot the containing subvolume, then COW starts to happen for new writes to either copy; overwrites to either copies newly written blocks are nocow. So anyway you can quickly get into complicated states with VM images on Btrfs. I'm not sure of the long term plan. This is how to set xattr +C at qcow2 create time, only applicable when the qcow2 is on Btrfs. # qemu-img create -o nocow=on But really piles more testing is needed to better understand some things with Btrfs and VMs. It's all quite complicated what's going on with these layers. Even though my VM images get monstrous numbers of fragments if I don't use +C, I haven't yet seen a big performance penalty as a result when the host and guest are using Btrfs and the cache is set to unsafe. Now, you might say, that's crazy! It's called unsafe for a reason! Yes, but I've also viscously killed the VM while writes were happening and at most I lose a bit of data that was in flight, the guest fs is not corrupt at all, not even any complaints on the remount. I've got limited testing killing the host while the writes are happening, and there is more data loss due to delayed allocation probably, but again the host and guest Btrfs are fine - no mount complaints at all. And you kinda hope the host isn't often dying... NTFS in qcow2 on Btrfs without +C however? From Btrfs list anecdote this combination appears to cause hundreds of thousands of fragments in short order, and serious performance penalties. But I haven't tested this. I'm guessing something about NTFS journalling and flushing, and suboptimal cache setting for libvirt is probably causing too aggressive flushes to disk and each flush is a separate extent. Just a guess. -- Chris Murphy

1 0

LVM hatred, was Re: /boot on a separate partition?
by Chris Murphy 25 Jun '15

25 Jun '15

Chris Adams linux at cmadams.net Wed Jun 24 13:14:34 UTC 2015 > > > There are plenty of people that have documented the performance > differences, just Google it. This is consistent with what I've experienced. Minimal difference. http://web-docs.gsi.de/~tstibor/iozone/qcow.vs.lvm/ -- Chris Murphy

1 0

LVM hatred, was Re: /boot on a separate partition?
by Chris Murphy 25 Jun '15

25 Jun '15

Mike - st257 silvertip257 at gmail.com Tue Jun 23 16:40:47 UTC 2015 > On Tue, Jun 23, 2015 at 12:15 PM, Jason Warr <jason at warr.net> wrote: > > I'm curious what has made some people hate LVM so much. I have been using > > it for years on thousands of > > No clue. > My experiences with LVM have been positive as well. > And in opinion it doesn't add much complexity (if you know the LVM tools, > you're fine). Flexibility is worth an ounce of complexity. I think LVM is badass, however if you don't know the LVM tools, you're instantly tossed deep into the weeds. Most every letter, lower and upper case, seems to be used twice by each of the lvm commands. I don't have enough fingers to count the number of lvm commands. There's so much intricate detail required for creating LVM layouts and doing snapshots and snapshot deletion compared to Btrfs that I've just about given up on LVM. I've also never had Btrfs snapshots explode on me like LVM thinp snapshots have when the metadata pool wasn't made big enough in advance (and it isn't made big enough by default, apparently). Most any typical maneuver done on LVM can be done much more easily and intuitively with Btrfs. So these days I just focus on Btrfs even though I definitely don't hate LVM. On desktop Linux, making LVM the default layout I think is a bad decision. It causes mortal users more trouble than it's worth. I'd be a bit more accommodating if LVM had integrated encryption with live bi-directional conversion. -- Chris Murphy

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss