From: sniper <s3c24xx@gmail.com>
To: "Yan, Zheng" <ukernel@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: bug when removing device
Date: Fri, 30 Apr 2010 21:37:54 +0800 [thread overview]
Message-ID: <k2i9bd6b5361004300637v6463b9f4w5e1348f74d2db06e@mail.gmail.com> (raw)
In-Reply-To: <p2u3d0408631004290158j40591c7coee8c6fc73c3d06d1@mail.gmail.com>
> I have sent a set of patches that address bugs like this.
>
I applied the V2 patchset to kernel-v2.6.32 (actually, I applied them
to btrfs-unstalbe, took a kernel-v2.6.32 and replaced its btrfs with
the patched one in btrfs-unstable), and did the test, then got:
$ sudo btrfs device del /dev/loop1 /tmp/mnt0/
ERROR: error removing the device '/dev/loop1'
$ sudo btrfs device del /dev/loop0 /tmp/mnt0/
ERROR: error removing the device '/dev/loop0'
dmesg:
[ 3463.136786] btrfs: unable to remove the only writeable device
[ 3468.205188] btrfs: unable to remove the only writeable device
Is it something wrong?
prev parent reply other threads:[~2010-04-30 13:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-28 18:11 bug when removing device sniper
2010-04-29 8:58 ` Yan, Zheng
2010-04-30 13:37 ` sniper [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=k2i9bd6b5361004300637v6463b9f4w5e1348f74d2db06e@mail.gmail.com \
--to=s3c24xx@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=ukernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).