From: Goffredo Baroncelli <kreijack@gmail.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
Stefan Behrens <sbehrens@giantdisaster.de>
Subject: Re: device delete, error removing device [SOLVED]
Date: Wed, 24 Oct 2012 23:30:53 +0200 [thread overview]
Message-ID: <50885E0D.9040701@gmail.com> (raw)
In-Reply-To: <D0E7C142-9FAE-4233-BA2E-BB1EB341FD93@colorremedies.com>
On 2012-10-24 21:13, Chris Murphy wrote:
>
> On Oct 24, 2012, at 12:06 PM, Goffredo Baroncelli
> <kreijack@gmail.com> wrote:
>>>
>>
>> I was able to reproduce it:
>>
>> - I filled the filesystem until I got "No space left on device".
>
> I didn't even need to get that far.
>
>
>> So it seems that I spread all the data to the other disk, filling
>> up the smaller ones. So it stuck to "No space left on device".
>>
>> Now I rebalanced with -dconvert=single, as suggested by Hugo, then
>> I was able to remove the disk:
>>
>> Label: 'test2' uuid: 11d0f1a8-2770-4ff2-8df5-f772f1056edc Total
>> devices 3 FS bytes used 7.63GB devid 4 size 12.00GB used 9.48GB
>> path /dev/vdf devid 3 size 3.00GB used 492.94MB path /dev/vdd
>> devid 2 size 3.00GB used 64.00MB path /dev/vdc
>
> It's an interesting solution, but difficult for a larger file system.
> Or at least, could be very time consuming.
It is not a solution but a workaround.
> Aside from the "no space left" problem, the 'device delete' behavior
> itself has kindof a high penalty: a successful 'device delete' on a
> five disk raid10 (one was added in advance of the delete), all disks
> are significantly written to, not merely a reconstruction of the
> replaced disk. It means a lot of writing to do disk removals in the
> face of an impending disk failure.
I am not telling that this is the right solution, I am telling that this
is the only solution available now :-(
However this page
https://btrfs.wiki.kernel.org/index.php/Project_ideas#Drive_swapping
states that someone is working on this kind of issue.
G.Baroncelli
>
>
> Chris Murphy
>
> -- 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
>
--
gpg @keyserver.linux.it: Goffredo Baroncelli (kreijackATinwind.it>
Key fingerprint BBF5 1610 0B64 DAC6 5F7D 17B2 0EDA 9B37 8B82 E0B5
next prev parent reply other threads:[~2012-10-24 21:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-22 4:32 device delete, error removing device Chris Murphy
2012-10-22 5:04 ` dima
2012-10-22 5:30 ` Chris Murphy
2012-10-22 6:02 ` Chris Murphy
2012-10-22 9:19 ` Hugo Mills
2012-10-22 16:42 ` Chris Murphy
2012-10-22 17:04 ` Goffredo Baroncelli
2012-10-22 19:36 ` Chris Murphy
2012-10-22 19:50 ` Hugo Mills
2012-10-22 20:35 ` Goffredo Baroncelli
2012-10-22 20:46 ` Chris Murphy
2012-10-22 17:18 ` Hugo Mills
2012-10-23 7:57 ` Michael Kjörling
2012-10-23 18:10 ` Goffredo Baroncelli
2012-10-23 18:17 ` Chris Murphy
2012-10-23 19:02 ` Goffredo Baroncelli
2012-10-23 20:28 ` Chris Murphy
2012-10-23 22:16 ` Goffredo Baroncelli
2012-10-23 22:29 ` Chris Murphy
2012-10-24 18:06 ` device delete, error removing device [SOLVED] Goffredo Baroncelli
2012-10-24 19:13 ` Chris Murphy
2012-10-24 21:30 ` Goffredo Baroncelli [this message]
2012-10-24 21:43 ` Chris Murphy
2012-10-25 19:26 ` Goffredo Baroncelli
2012-10-27 18:25 ` device delete, error removing device Chris Murphy
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=50885E0D.9040701@gmail.com \
--to=kreijack@gmail.com \
--cc=kreijack@inwind.it \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=sbehrens@giantdisaster.de \
/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).