From: Goffredo Baroncelli <kreijack@libero.it>
To: Lennert Buytenhek <buytenh@wantstofly.org>
Cc: linux-btrfs@vger.kernel.org, Miao Xie <miaox@cn.fujitsu.com>,
Josef Bacik <josef@redhat.com>
Subject: Re: problem re-adding original mount block device on multi-device fs
Date: Sat, 09 Jun 2012 07:35:38 +0200 [thread overview]
Message-ID: <4FD2E0AA.5040900@libero.it> (raw)
In-Reply-To: <20120608044210.GY725@wantstofly.org>
On 06/08/2012 06:42 AM, Lennert Buytenhek wrote:
> (please CC on replies, I'm not subscribed to the list)
>
> Hi!
>
> This fails:
>
> # mkfs.btrfs /dev/sd[bcde]
> # mount /dev/sdb /mnt/x
> # btrfs device delete /dev/sdb /mnt/x
> # btrfs device add /dev/sdb /mnt/x
> /dev/sdb is mounted
> #
>
> It seems that I have to unmount and remount the fs using another
> constituent block device before I can re-add the original block
> device that the filesystem was mounted with:
>
> # umount /mnt/x
> # mount /dev/sdb /mnt/x
> mount: wrong fs type, bad option, bad superblock on /dev/sdb,
> missing codepage or helper program, or other error
> In some cases useful info is found in syslog - try
> dmesg | tail or so
> # mount /dev/sdc /mnt/x
> # btrfs device add /dev/sdb /mnt/x
> #
>
> This is on up-to-date F17, kernel 3.4.0(-1.fc17) with btrfs-progs
> 0.19(-18.fc17).
Give a look to this patche:
[PATCH 2/2] Btrfs: fix wrong the mount information in /proc
This should address (even without solving) this kind of problem.
>
>
> thanks,
> Lennert
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> .
>
prev parent reply other threads:[~2012-06-09 5:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-08 4:42 problem re-adding original mount block device on multi-device fs Lennert Buytenhek
2012-06-09 5:35 ` Goffredo Baroncelli [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=4FD2E0AA.5040900@libero.it \
--to=kreijack@libero.it \
--cc=buytenh@wantstofly.org \
--cc=josef@redhat.com \
--cc=kreijack@inwind.it \
--cc=linux-btrfs@vger.kernel.org \
--cc=miaox@cn.fujitsu.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.