8

In my situation, it's for a local build/staging server running ubuntu server. Things I'd like to know are:

Why I should/shouldn't use LVM?

What problems might it cause in terms of either regular server operation or things I might want to do later? (ex. partitioning)

Why I should/shouldn't use encrypted LVM instead of LVM?

What problems might encrypted LVM cause in terms of either regular server operation or things I might want to do later? (ex. partitioning)

user29600
  • 419
  • 5
  • 17
  • 30

1 Answers1

7

LVM makes managing partitions a lot easier. Most Linux filesystems can be expanded these days, and expanding a partition (or Logical Volume as they're called in LVM) is a LOT easier than it is with MBR or GPT partition tables. The enhanced flexibility it provides is the main reason people use it.

When creating your set up, don't allocate all of your disk to your Logical Volumes, leave some slack. When those filesystems grow to the point they need more space, just Expand it using some of your saved space. This is a very easy operation, and unlike MBR/GPT the actual data area doesn't even have to be contiguous.

LVM does extend the code-path for getting data to actual drives, but it is very battle-tested by now. There are very few cases where I would NOT use LVM.

sysadmin1138
  • 133,124
  • 18
  • 176
  • 300
  • Exactly what I was looking for, thanks! What about encrypted LVM? – user29600 Apr 07 '11 at 15:31
  • @user29600 I have no experience with them, so others will have to comment. – sysadmin1138 Apr 07 '11 at 15:32
  • Why do you suggest leaving some slack? And how much? – user29600 Apr 07 '11 at 15:33
  • @user29600 That's just to enhance your ability to manage things in the future, since very few filesystems support *shrinking*. If you allocate everything now, fixing your bad assumptions in 3 years is a lot harder than if you just allocate some now. – sysadmin1138 Apr 07 '11 at 15:35