Linked by Thom Holwerda on Tue 10th Mar 2009 15:05 UTC, submitted by vijayd81
Permalink for comment 352658
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 06/13/13 14:35 UTC
Linked by Thom Holwerda on 06/11/13 17:07 UTC
Linked by Thom Holwerda on 06/10/13 23:13 UTC
Linked by Thom Holwerda on 06/08/13 14:57 UTC
Linked by Thom Holwerda on 06/07/13 11:40 UTC
Linked by Thom Holwerda on 06/04/13 12:45 UTC
Linked by nfeske on 05/31/13 10:12 UTC
Linked by Thom Holwerda on 05/29/13 16:59 UTC
Linked by Thom Holwerda on 05/24/13 17:26 UTC
Linked by Thom Holwerda on 05/21/13 21:38 UTC
More Features »
Sponsored Links



Member since:
2009-03-11
ext3 and xfs are a bit slower on LVM, because LVM doesn't support barriers. Also there are cases when xfs stacked atop LVM stacked atop other drivers can overflow x86's 4kB kernel stack. It's also possible to make a mess of the mappings, so the logical block numbers of the virtual device are randomly scattered across the physical devices. That takes quite a bit of effort to achieve, though
What we call LVM these days is actually LVM2, built on top of Linux 2.6's device-mapper (LVM1 is Linux 2.4's volume manager). EVMS used to be a nice front-end to LVM, but is kinda unmaintained nowadays. mdadm handles RAID, which you might think would be part of volume management, but dm only supports RAID-1 for now.
Going proprietary, VxVM (Veritas Volume Manager) is available for Linux too. I have no idea how it compares.