[kwlug-disc] Disk longevity ...

[Bob Jonkman]

On current OSes the LVM stuff seems to be installed as part of the base 
operating system; I can see LVs with lsblk and I can just mount the LVs 
as either /dev/mapper/volumegroup-lvname or /dev/volumegroup/lvname  For 
some reason I almost always use the /dev/mapper/volumegroup-lvname syntax...

On older versions of Debian or Ubuntu (2012?) it might be necessary to 
install the lvm2 package. But I've found that the package installation 
makes sure all the needed OS components are in place, and then the LVs 
are available with the above syntax. There' no extra effort for the 
SysAdmin.

Older GRUB couldn't boot directly from LVs, but for the last five years 
or so GRUB recognizes LVM, so I no longer create a separate /boot 
partition outside the LVs. The only time I create a separate /boot 
partition now is for encrypted drives.

--Bob.


On 2022-02-15 19:04, Chris Frey wrote:
> On Tue, Feb 15, 2022 at 05:57:49PM -0500, Bob Jonkman wrote:
>> When I set up new servers I create a few extra LVs each 15 GB in size for
>> "spare" and "backupOS" which I use for a clean install of a new OS, install
>> the packages (with dpkg --set-selections), and then point the new fstab to
>> the old LVs for /home, /srv, /opt, /var/lib/mysql or /var/lib/postgresql,
>> and /usr/local, and copy the necessary config files from the former root
>> LV's /etc (yes, salt or ansible would be useful here).
> 
> What do you use to get the new LVs started?  Do you run the usual
> installer and just tell it the new LVs to use?
> 
> Thanks,
> - Chris
> 
> 
> _______________________________________________
> kwlug-disc mailing list
> kwlug-disc at kwlug.org
> https://kwlug.org/mailman/listinfo/kwlug-disc_kwlug.org

-- 
Bob Jonkman <bjonkman at sobac.com>          Phone: +1-519-635-9413
SOBAC Microcomputer Services             http://sobac.com/sobac/
Software   ---   Office & Business Automation   ---   Consulting
GnuPG Fngrprnt:04F7 742B 8F54 C40A E115 26C2 B912 89B0 D2CC E5EA