Re: a filesystem for partitions
From: Frank Sweetser (fs_at_erwin.wpi.edu)
Date: 08/12/03
- Next message: Duke Robillard: "Re: forking a process that has multiple threads"
- Previous message: phil-news-nospam_at_ipal.net: "Re: Fast memcpy in kernel space"
- In reply to: phil-news-nospam_at_ipal.net: "Re: a filesystem for partitions"
- Next in thread: phil-news-nospam_at_ipal.net: "Re: a filesystem for partitions"
- Reply: phil-news-nospam_at_ipal.net: "Re: a filesystem for partitions"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 12 Aug 2003 16:36:23 +0000 (UTC)
phil-news-nospam@ipal.net <phil-news-nospam@ipal.net> wrote:
>| Why not just use LVM? Add the devices to a VG and make LVs out of it instead
>| of creating a slew of block devices for each partition.
>
> I have the understanding that LVM adds its own overhead to the storage space.
> Or are you just saying to hack the LVM code to only make use of its device
> space?
Yes, LVM uses space - but so does a partition table. This has the advantage
that you don't have to patch anything, but can just leverage existing tools.
-- Frank Sweetser fs at wpi.edu WPI Network Engineer
- Next message: Duke Robillard: "Re: forking a process that has multiple threads"
- Previous message: phil-news-nospam_at_ipal.net: "Re: Fast memcpy in kernel space"
- In reply to: phil-news-nospam_at_ipal.net: "Re: a filesystem for partitions"
- Next in thread: phil-news-nospam_at_ipal.net: "Re: a filesystem for partitions"
- Reply: phil-news-nospam_at_ipal.net: "Re: a filesystem for partitions"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|