From: Steven Post <redalert.commander@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Device delete returns "unable to go below four devices on raid10" on 5 drive setup
Date: Sun, 01 Sep 2013 23:43:47 +0200 [thread overview]
Message-ID: <1378071827.5456.3.camel@pc-steven.LAN> (raw)
In-Reply-To: <1378037326.4694.13.camel@pc-steven.LAN>
[-- Attachment #1: Type: text/plain, Size: 1314 bytes --]
On Sun, 2013-09-01 at 14:08 +0200, Steven Post wrote:
> On Sat, 2013-08-31 at 18:03 -0600, Chris Murphy wrote:
> > On Aug 31, 2013, at 5:55 PM, Steven Post <redalert.commander@gmail.com> wrote:
> >
> > > On Sat, 2013-08-31 at 11:42 -0600, Chris Murphy wrote:
> > >>
> > >> Yes. It might take a few minutes after the chunks are reallocated for the device to be removed from the volume. I've had some cases where even a reboot was needed for the information in fi sh to refresh.
> > >
> > > I see, so that might be normal behaviour.
> >
> > No, I think it's expected for deleted devices to not appear in the volume listing anymore, but with older kernels I had that experience. I haven't tried it recently with newer kernels.
>
> I might have phrased that a bit incorrectly, with 'normal behaviour' I
> meant it was known to do that and not cause major problems. Of course I
> would expect the entry to just disappear.
> I'll let you know the result of the 'device delete' operation on the
> second machine (3.10.7 kernel).
The 3.10.7 kernel doesn't seem to have this issue, the removed device is
not listed anymore immediately after the 'device delete' command
returns. Although in that instance the array still had 6 drives, not 5
as with the old one.
[...]
Best regards,
Steven
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
prev parent reply other threads:[~2013-09-01 21:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-31 10:12 Device delete returns "unable to go below four devices on raid10" on 5 drive setup Steven Post
2013-08-31 11:41 ` Duncan
2013-08-31 17:42 ` Chris Murphy
2013-08-31 22:20 ` Hugo Mills
2013-08-31 23:55 ` Steven Post
2013-09-01 0:03 ` Chris Murphy
2013-09-01 12:08 ` Steven Post
2013-09-01 21:43 ` Steven Post [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=1378071827.5456.3.camel@pc-steven.LAN \
--to=redalert.commander@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).