Talk:LVM
Before creating a discussion or leaving a comment, please read about using talk pages. To create a new discussion, click here. Comments on an existing discussion should be signed using
~~~~:
A comment [[User:Larry|Larry]] 13:52, 13 May 2024 (UTC) : A reply [[User:Sally|Sally]] 09:13, 5 November 2024 (UTC) :: Your reply ~~~~
RAID5
LVM2 RAID5 - looks scary, if you define the LV size as 20% of the VG(which is for 6GB VG 1.2GB LV) and 2 stripes, it just takes 50% extra space and uses 1.8GB in the VG. Maybe a note would be useful? Disi 17:00, 4 November 2011 (UTC)
- Its only example. Better to define actual wanted size.
- -- Alexxy 15:44, 13. Nov. 2011 (UTC)
systemd
There is no lvm.service. All I have right now (provided by sys-fs/lvm2:
/usr/lib/systemd/system/lvm2-monitor.service /usr/lib/systemd/system/blk-availability.service /usr/lib/systemd/system/lvm2-lvmetad.service /usr/lib/systemd/system/dm-event.service
— The preceding unsigned comment was added by Eliasp (talk • contribs) 17 February 2014
Does the udev USE flag affect eudev too?
Does the udev flag affect both sys-fs/udev and sys-fs/eudev ? I am guessing yes because eudev is a fork, and only one of them can be installed at the same time. Would someone confirm and maybe update the description for 'udev' USE flag in the article? Thank --EmanueLczirai (talk) 09:50, 13 January 2015 (UTC)
- Yes it does. However, the USE flags are automatically generated from the repository (when package.gentoo.org provides them correctly). This cannot be updated by hand in the article. --Grknight (talk) 21:21, 7 November 2018 (UTC)
lvmetad warning
I am getting a warning after executing pvcreate /dev/sd[ab]1 from the InstallCD which shows WARNING: lvmetad is running but disabled. Restart lvmetad before enabling it!. I am unsure how to handle this, as the article doesn't mention it. Do I even need lvmetad ? Maybe I don't need it while installing but what about afterwards, while the system is running normally? Should I do /etc/init.d/lvmetad stop prior to pvcreate, just to be sure? (If I do, I don't get the warning). If the warning is harmless, please consider updating the article stating so. Thanks in advance --EmanueLczirai (talk) 03:35, 15 January 2015 (UTC)
- Apparently, in my case (LVM on a single disk: 1 PV, 1 VG, 2 LVs(bootvol+rootvol both btrfs); +grub2(with 2M bios partition near the huge LVM 8e00 partition)), it works without lvmetad(and even lvm) both while installing and afterwards. In the latter case I made sure lvmetad doesn't start by issuing this once rc-update del lvm boot. And now this shows lvm* aren't started in any runlevels: rc-update -v show|grep -i lvm. I might be missing something about this, I guess we'll find out(?). --EmanueLczirai (talk) 07:07, 18 January 2015 (UTC)
- lvmetad is for "if you want to enable lvm autoactivation and metadata caching", says lvm2 after emerging. --EmanueLczirai (talk) 14:12, 10 February 2015 (UTC)
- Normally lvmetad is not even enabled. Neither in initscripts nor in /etc/lvm/lvm.conf. But the lvm service has a useless rc_need on lvmetad. Remove it to get rid of those messages. Morbid Florist (talk) 15:20, 22 July 2015 (UTC)
- This discussion is seven years old, and seems probably no longer active. Closing discussion as per Help:Talk_pages#Closing_discussions, please reopen if necessary. -- Ris (talk) 17:05, 19 February 2022 (UTC)
A note about installing gentoo on LVM from InstallCD
If you are like me, using InstallCD(livecd?) to create LVM volumes and you had to interrupt the manual gentoo installation process only to resume it the next day, the next time you boot(from installcd), before chrooting, mounting these LVM volumes requires activating them like this lvchange --verbose --activate y --activationmode complete volgroupnamehere (or simpler lvchange -ay volgroupnamehere) otherwise the folder /dev/volgroupnamehere/ (eg. /dev/volgroupnamehere/logicalvolumenamehere_root which you need to mount root) does not exist. --EmanueLczirai (talk) 23:47, 15 January 2015 (UTC)
- I'm actually using
vgchange -ayand that seems to activate everything. Also a note about renaming a vg when you have duplicate names (e.g. when you connect a disk with your older installation using a USB-SATA connector) would be useful. --Pavlix (talk) 18:17, 10 February 2015 (UTC)
Handbook section
The whole section Handbook added by this change does not well integrate with the rest of the article. It does not leave any choice, stresses GRUB genkernel and unnecessarily duplicates information from other wiki articles. I'd like to propose moving it to somewhere else (maybe a separate subarticle) or remove it.
Any objections?--Charles17 (talk) 07:42, 23 December 2017 (UTC)
- I added the Handbook section there because I wasn't entirely sure where to put it, I wanted to compliment the handbook as it was lacking LVM content. While it only has grub and does duplicate information from other articles it does provide step-by-step instructions to help the end user accomplish the task. A separate article would be a good idea and have the handbook linked to it. I'm kinda new to editing these wiki's and documentation so apologies if I have missed something or overstepped the mark. — The preceding unsigned comment was added by Box293 (talk • contribs) 04:27, 24 December 2017
- No reason to excuse for bringing good new content to the wiki. And the question where information should be placed is always a matter of personal opinion. Some people like repeating content identically in many articles. I prefer to have it once per topic and to refer to it where needed. And sometimes it's hard to decide to which main article new subarticles (e.g. different ways for creating an LVM specific initramfs) should go. Experienced authors are also having lots of articles under their user ... --Charles17 (talk) 10:19, 24 December 2017 (UTC)
- Seems this section was removed in later change. Closing discussion as per Help:Talk_pages#Closing_discussions, please reopen if necessary. -- Ris (talk) 17:10, 19 February 2022 (UTC)
Configuring the bootloader section
In Section 1.4.4 Configuring the bootloader there seems to be a step missing.
Section 1.4.4.1 Emerge shows the pre-req needed prior to actually emerging GRUB:2, but does not actually contain the emerge statement. That command is actually located in Section 1.4.4.2 Install. However, the output shown under that command is actually for the installation command(s), as described in the Handbook Handbook:AMD64/Installation/Bootloader#Install_2.
So, it seems (to me, at least) that the actual command needed to install GRUB2 is missing from the wiki.
I would edit it myself, but I'm not 100% sure of the scope needed to be covered here (the entire Handbook install section commands, just MBR / EFI, etc.) - so I opened this talk for your perusal. I kept it under the Handbook talk as well because it seemed to fit, based upon the rest of the talk.
Forgive me is I did this incorrectly - I asked in the forums and was told I could edit the wiki directly, or post here - and I took Neddy up on his suggestion. johngalt (talk) 03:13, 13 July 2018 (UTC)
Example outputs
I noticed that in "3.1.3 Create lvm", the output of pvcreate /dev/sd[ab]1 is has shown a predefined volume group (VG) name where none should have existed. Is this something we want to clarify? Link: LVM#Create_PV Egberts (talk) 17:22, 8 September 2022 (UTC)
- I read this differently as this is the Usage section. "List PV" is talking about how people normally see it after assigned to a volume group. This continues with "Remove PV" later on. The "Create PV" is not directly related to "List PV" or "Remove PV". --Grknight (talk) 13:07, 9 September 2022 (UTC)
Wrong partition type for Linux LVM
Hi, this page says partition type for Linux LVM is 43, but according to wiki and list inside fdisk it is 8E. https://en.wikipedia.org/wiki/Partition_type#List_of_partition_IDs Lekto (talk) 16:28, 17 November 2023 (UTC)