On Mon, 2008-06-09 at 14:45 +0100, Miguel Sousa Filipe wrote: > Hi all, > > On Mon, Jun 9, 2008 at 11:06 AM, Chris Mason <[EMAIL PROTECTED]> wrote: > > On Mon, 9 Jun 2008 02:43:58 -0400 > > Christoph Hellwig <[EMAIL PROTECTED]> wrote: > > > >> On Sat, Jun 07, 2008 at 05:53:37PM -0600, > > > >> Yes, I plan to work on adding properly designed multiple device > >> support for btrfs and my upcoming similar xfs work. I'll live in > >> good old mount and libvolume_id. > >> > > > > I won't say no to a mount patch either. The only downside is that > > we'll need to update it (in mount) as the format goes through changes > > over the summer. But that is a temporary problem. > > > I believe that a multi-volume filesystem should have some kind of > human understandable handle/name. > Just like a name of a logical volume. For single disks filesystems, > the disk name suffices (and reduced the need for such a name/label), > but in multi-disk FS there should still be a humane name for that > mountpoint or filesystem. > So, while any unique identifier would technically be okay, I think > that there should be a human undertanble name/label for it. Not just > some uid. > > Does Hellwig work, or any planned feature provide this ?
mkfs.btrfs already has a way to set the label of the filesystem. mkfs.btrfs -L label /dev/xxxx btrfs-show will show you the labels of any existing filesystems. In practice, anyone on a san really wants to use uuids. Labels are nice until two people on the same san create a filesystem named system, and then it all gets ugly ;) -chris -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
