the LVM volume can be seen as sort of dynamic disk， which may not be recognized by another machine when the original system is collapsed.
As a result, what should be done to ensure that I can restore the data on the disk when the OS is dead.
the potential risk of LVM volume
-
Avoid using multi disk volume groups.
-
-
LVM should be able to transfer between machines. This is not an uncommon practice for data volumes, and was particularly useful when drives were small and you needed a large number to make a large volume or when used in enterprise level setups where smaller volumes had to be provisioned on a large block of drives.
Personally though, I think LVM adds a layer of complexity that is not needed for most OMV users and to some degree an added place for something to go wrong.
If you want to grow the size of a volume at a later date, have a look at the mergefs or snapraid plugin. Mergefs essentially takes a bunch of stand alone drives and puts them in a storage pool that can be expanded, but the drives are still really stand alone drives.
Snapraid take the idea a step further by offering a parity setup similar to an actual RAID to help protect against a drive failing.
-
is that means we should abandon the convenience of expanding the space of the lvm ???
Then there is no need to install lvm2 ?
Are you using lvm to pool disks? lvm makes sense on virtual machines where you can change the size of a disk. On hardware, this makes less sense. You can expand the space of anything without LVM too. I use LVM all day long at work but don't use it at home because it doesn't make sense to use it.
Participate now!
Don’t have an account yet? Register yourself now and be a part of our community!