All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: Christian Hesse <mail@earthworm.de>
Cc: btrfs-devel@oss.oracle.com,
	Miguel Sousa Filipe <miguel.filipe@gmail.com>,
	Christoph Hellwig <hch@infradead.org>,
	btrfs-devel@arbitraryconstant.com, linux-btrfs@vger.kernel.org
Subject: Re: btrfs device management
Date: Mon, 09 Jun 2008 12:22:29 -0400	[thread overview]
Message-ID: <1213028549.10187.51.camel@think.oraclecorp.com> (raw)
In-Reply-To: <200806091819.18985.mail@earthworm.de>

On Mon, 2008-06-09 at 18:19 +0200, Christian Hesse wrote:
> On Monday 09 June 2008, Miguel Sousa Filipe wrote:
> > On Mon, Jun 9, 2008 at 2:52 PM, Chris Mason <chris.mason@oracle.com> wrote:
> > > 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.
> >
> > Can I mount by label ?
> > something like:
> > # mount /dev/btrfs/label /mountpoint
> 
> Yes, by mounting /dev/disk/by-label/label. That should work with every block 
> device.

Once btrfs support is in libblkid (or whatever udev uses) that is.
Today btrfs won't show up in /dev/disk/by-label/label or mount -L

-chris



      reply	other threads:[~2008-06-09 16:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-07 23:53 btrfs device management btrfs-devel
2008-06-09  1:45 ` Chris Mason
2008-06-09  6:43 ` Christoph Hellwig
2008-06-09 10:06   ` Chris Mason
2008-06-09 13:45     ` Miguel Sousa Filipe
2008-06-09 13:52       ` Chris Mason
2008-06-09 15:37         ` Miguel Sousa Filipe
2008-06-09 16:19           ` Christian Hesse
2008-06-09 16:22             ` Chris Mason [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1213028549.10187.51.camel@think.oraclecorp.com \
    --to=chris.mason@oracle.com \
    --cc=btrfs-devel@arbitraryconstant.com \
    --cc=btrfs-devel@oss.oracle.com \
    --cc=hch@infradead.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=mail@earthworm.de \
    --cc=miguel.filipe@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.