From: Chris Mason <chris.mason@oracle.com>
To: Hugo Mills <hugo-lkml@carfax.org.uk>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Problem with renaming devices
Date: Tue, 07 Apr 2009 07:35:56 -0400 [thread overview]
Message-ID: <1239104156.17426.26.camel@think.oraclecorp.com> (raw)
In-Reply-To: <20090406174135.GC27111@vlad.carfax.org.uk>
On Mon, 2009-04-06 at 18:41 +0100, Hugo Mills wrote:
> There seems to be some issue over changing the names of the device
> that a btrfs filesystem lives on:
>
> # lvcreate scratch -n fstest -L 2G
> Logical volume "fstest" created
> # mkfs -t btrfs /dev/scratch/fstest
>
> WARNING! - Btrfs v0.18-ge3b0f66 IS EXPERIMENTAL
> WARNING! - see http://btrfs.wiki.kernel.org before using
>
> fs created label (null) on /dev/scratch/fs1
> nodesize 4096 leafsize 4096 sectorsize 4096 size 2.00GB
> Btrfs v0.18-ge3b0f66
>
> # mount /dev/scratch/fstest /mnt
> # umount /mnt
>
> # lvrename scratch fstest derek
> Renamed "fstest" to "derek" in volume group "scratch"
> # mount /dev/scratch/derek /mnt
> mount: /dev/mapper/scratch-derek: can't read superblock
>
> # lvrename scratch derek fstest
> Renamed "derek" to "fstest" in volume group "scratch"
> # mount /dev/scratch/fstest /mnt
> [success]
>
> The rename works properly on a completely virgin filesystem, but
> not on one that's been mounted and unmounted (as above).
Whoops, we need to reset the pathname when a probe finds a given dev
uuid on a given device. I'll patch it up when I get back next week.
Thanks for this bug report.
-chris
next prev parent reply other threads:[~2009-04-07 11:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-06 17:41 Problem with renaming devices Hugo Mills
2009-04-07 11:35 ` Chris Mason [this message]
[not found] <69e11d1f0911071341n4c0a845ds7bbf5d64b039d8f@mail.gmail.com>
2009-11-07 21:44 ` Gustavo Alves
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=1239104156.17426.26.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=hugo-lkml@carfax.org.uk \
--cc=linux-btrfs@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox