From: "Piotr Pawłow" <pp@siedziba.pl>
To: linux-btrfs@vger.kernel.org
Subject: Re: Help! - "btrfs device delete missing" running out of space
Date: Sun, 5 Jan 2014 19:00:34 +0000 (UTC) [thread overview]
Message-ID: <laca4i$7lq$1@ger.gmane.org> (raw)
In-Reply-To: labocc$5ue$1@ger.gmane.org
Hello,
> distribution, used space on each device should be accordingly: 160,
> 216, and 405.
The last number should be 376, I copied the wrong one. Anyway, I deleted
as much data as possible, which probably won't help in the end, but at
the moment it's still going. Meanwhile, I made a script to replicate this
problem:
http://pastebin.com/W2c2pJYp
On kernel 3.12.6 the output is:
-------
WARNING! - Btrfs v0.20-rc1 IS EXPERIMENTAL
WARNING! - see http://btrfs.wiki.kernel.org before using
adding device /dev/loop1 id 2
fs created label (null) on /dev/loop0
nodesize 4096 leafsize 4096 sectorsize 4096 size 40.00GB
Btrfs v0.20-rc1
17000+0 records in
17000+0 records out
17825792000 bytes (18 GB) copied, 533,571 s, 33,4 MB/s
Label: none uuid: f8a01060-94c2-4665-b5ff-f134f9b6ad9b
Total devices 2 FS bytes used 16.63GB
devid 2 size 20.00GB used 18.01GB path /dev/loop1
devid 1 size 20.00GB used 18.03GB path /dev/loop0
Btrfs v0.20-rc1
ERROR: error removing the device 'missing' - No space left on device
Label: none uuid: f8a01060-94c2-4665-b5ff-f134f9b6ad9b
Total devices 4 FS bytes used 16.62GB
devid 4 size 10.00GB used 9.03GB path /dev/loop3
devid 3 size 10.00GB used 9.25GB path /dev/loop2
devid 1 size 20.00GB used 12.31GB path /dev/loop0
*** Some devices missing
Btrfs v0.20-rc1
-------
The "delete missing" logic is pretty much broken, at least in this case.
Instead of just replicating the data to other drives, it moves some of
the data which fills up smaller drives and it fails with "No space left
on device" error.
Regards
next prev parent reply other threads:[~2014-01-05 19:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-05 13:57 Help! - "btrfs device delete missing" running out of space Piotr Pawłow
2014-01-05 19:00 ` Piotr Pawłow [this message]
2014-01-06 16:24 ` Calvin Walton
2014-01-06 18:44 ` Piotr Pawłow
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='laca4i$7lq$1@ger.gmane.org' \
--to=pp@siedziba.pl \
--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 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.