From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: Timothy Normand Miller <theosib@gmail.com>
Cc: Qu Wenruo <quwenruo@cn.fujitsu.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs-image gets stuck, using 100%, looping on bad file descriptor
Date: Thu, 20 Aug 2015 09:12:36 -0400 [thread overview]
Message-ID: <55D5D244.6070507@gmail.com> (raw)
In-Reply-To: <CAK7bmU9h0s_cTY+r8b7EbvD6nAvK0NafGVace5+3yTFanT0M1A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 595 bytes --]
On 2015-08-20 09:08, Timothy Normand Miller wrote:
> On Thu, Aug 20, 2015 at 7:38 AM, Austin S Hemmelgarn
> <ahferroin7@gmail.com> wrote:
>
>> Just for reference, I've found that it is usually safer to delete the
>> missing device first if possible, then add the new one and re-balance. There
>> seem to be some edge-cases in the code for deleting missing devices.
>>
>
> The problem is that you can't do that if there's not enough space on
> the remaining devices to hold all the data.
>
>
Good point, I often forget that not everyone over-provisions their
storage like I do.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3019 bytes --]
next prev parent reply other threads:[~2015-08-20 13:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-18 15:40 btrfs-image gets stuck, using 100%, looping on bad file descriptor Timothy Normand Miller
2015-08-19 1:32 ` Qu Wenruo
2015-08-19 2:46 ` Timothy Normand Miller
2015-08-19 2:48 ` Qu Wenruo
2015-08-19 2:55 ` Timothy Normand Miller
2015-08-19 5:22 ` Qu Wenruo
2015-08-19 16:18 ` Timothy Normand Miller
2015-08-20 11:38 ` Austin S Hemmelgarn
2015-08-20 13:08 ` Timothy Normand Miller
2015-08-20 13:12 ` Austin S Hemmelgarn [this message]
2015-08-21 1:32 ` Qu Wenruo
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=55D5D244.6070507@gmail.com \
--to=ahferroin7@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo@cn.fujitsu.com \
--cc=theosib@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).