[NTLUG:Discuss] How do I protect drives configured with LVM fromfdisk?

[Mark Hanna]

partition type 8E denotes Linux LVM in fdisk.

test, Test, TEST this first but you should be able to create one single partition in fdisk, mark it as 8E and not lose anything.  be sure to reboot after you write the table.

The problem from what I'm seeing in your test is that you created the LVM first and then the mkfs afterwards.  If you start witht he filesystem LVM'd and a filesystem on it, changes via fdisk shouldn't affect it.

and if you don't test this first and lose any data, you'll get whatever the god Randomis Factoris decides to throw at you...

Been my experience anyway.  I've made all kinds of crazy changes via fdisk, saved them and then changed them back without losing data... 

hmmm... I may have to test this exact scenario when I get home tonight

>>> ntlug at rain4us.net 12/10/04 02:59PM >>>
I've been working with an LVM2 solution using a bank of eight 250gig SATA
drives on a 3ware controller.  I'm getting pretty comfortable with using
LVM as a solution, but I have just ONE concern.  An inexperienced netadmin
could come in, see available unpartitioned disk space as reported by
fdisk/cfdisk and proceed to wipe out an LVM volume.


As a test, I created an LVM volume un an unpartitioned drive... proceded
to partition it via cfdisk, mkreiserfs the volume, and mount it.  All went
well..except I lost the test files on my LVM'ed volume.

How does one protect the disks being used by LVM from the ravages of those
uninitiated to the glories of LVM?  --or-- am I missing an important step
in the creation of my PE/VG/LVs?

-- 
Richard



_______________________________________________
https://ntlug.org/mailman/listinfo/discuss