From: Ronan Arraes Jardim Chagas <ronisbr@gmail.com>
To: Jeff Mahoney <jeffm@suse.com>,
Chris Murphy <lists@colorremedies.com>,
"Austin S. Hemmelgarn" <ahferroin7@gmail.com>
Cc: Wang Xiaoguang <wangxg.fnst@cn.fujitsu.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>,
Qu Wenruo <quwenruo@cn.fujitsu.com>
Subject: Re: BTRFS constantly reports "No space left on device" even with a huge unallocated space
Date: Fri, 02 Sep 2016 16:56:21 -0300 [thread overview]
Message-ID: <1472846181.13263.2.camel@gmail.com> (raw)
In-Reply-To: <506f2875-8cea-2d99-3664-52ee546adcfd@suse.com>
Hi again guys!
After I rebooted the computer, I still can't run balance on metatada:
btrfs balance start -musage=1 /
ERROR: error during balancing '/': No space left on device
There may be more info in syslog - try dmesg | tail
dmesg shows:
[ 2022.530285] BTRFS info (device sda6): relocating block group
128509280256 flags 36
[ 2023.355206] BTRFS info (device sda6): relocating block group
127972409344 flags 36
[ 2024.265313] BTRFS info (device sda6): relocating block group
127435538432 flags 36
[ 2025.646712] BTRFS info (device sda6): relocating block group
126898667520 flags 36
[ 2026.794791] BTRFS info (device sda6): relocating block group
126361796608 flags 36
[ 2028.023517] BTRFS info (device sda6): relocating block group
125824925696 flags 36
[ 2028.881287] BTRFS info (device sda6): relocating block group
125288054784 flags 36
[ 2029.739342] BTRFS info (device sda6): relocating block group
124751183872 flags 36
[ 2030.631990] BTRFS info (device sda6): relocating block group
124214312960 flags 36
[ 2031.523176] BTRFS info (device sda6): relocating block group
123677442048 flags 36
[ 2032.407859] BTRFS info (device sda6): relocating block group
123140571136 flags 36
[ 2033.806672] BTRFS info (device sda6): relocating block group
122603700224 flags 36
[ 2035.237712] BTRFS info (device sda6): relocating block group
122066829312 flags 36
[ 2038.257268] BTRFS info (device sda6): relocating block group
122033274880 flags 34
[ 2039.911443] BTRFS info (device sda6): relocating block group
121496403968 flags 36
[ 2040.958106] BTRFS info (device sda6): relocating block group
120959533056 flags 36
[ 2041.841051] BTRFS info (device sda6): relocating block group
120422662144 flags 36
[ 2042.828359] BTRFS info (device sda6): relocating block group
119885791232 flags 36
[ 2044.297744] BTRFS info (device sda6): relocating block group
119348920320 flags 36
[ 2045.684932] BTRFS info (device sda6): relocating block group
118812049408 flags 36
[ 2046.761787] BTRFS info (device sda6): relocating block group
118275178496 flags 36
[ 2048.200756] BTRFS info (device sda6): relocating block group
117738307584 flags 36
[ 2049.806986] BTRFS info (device sda6): relocating block group
117201436672 flags 36
[ 2051.170470] BTRFS info (device sda6): relocating block group
116664565760 flags 36
[ 2051.910536] BTRFS info (device sda6): relocating block group
116127694848 flags 36
[ 2052.678395] BTRFS info (device sda6): relocating block group
115590823936 flags 36
[ 2053.737959] BTRFS info (device sda6): relocating block group
106363355136 flags 36
[ 2054.852065] BTRFS info (device sda6): relocating block group
105826484224 flags 36
[ 2055.911187] BTRFS info (device sda6): relocating block group
105222504448 flags 36
[ 2057.047407] BTRFS info (device sda6): 4 enospc errors during balance
and I have:
btrfs fi usage /
Overall:
Device size: 1.26TiB
Device allocated: 80.07GiB
Device unallocated: 1.18TiB
Device missing: 0.00B
Used: 41.95GiB
Free (estimated): 1.18TiB (min: 603.95GiB)
Data ratio: 1.00
Metadata ratio: 2.00
Global reserve: 352.00MiB (used: 576.00KiB)
Data,single: Size:40.01GiB, Used:39.95GiB
/dev/sda6 40.01GiB
Metadata,DUP: Size:20.00GiB, Used:1.00GiB
/dev/sda6 40.00GiB
System,DUP: Size:32.00MiB, Used:16.00KiB
/dev/sda6 64.00MiB
Unallocated:
/dev/sda6 1.18TiB
Hope this brings new information!
Best regards,
Ronan Arraes
next prev parent reply other threads:[~2016-09-02 19:56 UTC|newest]
Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-12 17:36 BTRFS constantly reports "No space left on device" even with a huge unallocated space Ronan Arraes Jardim Chagas
2016-08-12 18:02 ` Chris Murphy
2016-08-12 19:00 ` Ronan Arraes Jardim Chagas
2016-08-12 19:37 ` Chris Murphy
2016-08-12 20:34 ` Chris Murphy
[not found] ` <CAKdnfRJeOXHmrumDkfxLTf-nU=KwZ0f7ybET-3o7kwwJDOZ2aw@mail.gmail.com>
2016-08-15 23:24 ` Chris Murphy
2016-08-16 17:49 ` Ronan Arraes Jardim Chagas
2016-08-22 19:11 ` Ronan Arraes Jardim Chagas
2016-08-22 20:39 ` Ronan Arraes Jardim Chagas
2016-08-22 20:49 ` Chris Murphy
2016-08-22 21:04 ` Ronan Arraes Jardim Chagas
2016-08-24 0:40 ` Jeff Mahoney
2016-08-25 15:58 ` Lutz Vieweg
2016-08-25 23:56 ` Chris Murphy
2016-08-26 5:59 ` Marc Haber
2016-08-29 12:12 ` Wang Xiaoguang
2016-08-29 13:20 ` Ronan Arraes Jardim Chagas
2016-08-29 15:52 ` Ronan Arraes Jardim Chagas
2016-08-29 22:25 ` Jeff Mahoney
2016-08-30 2:12 ` Wang Xiaoguang
2016-08-30 12:50 ` Ronan Arraes Jardim Chagas
2016-08-30 16:44 ` Chris Murphy
2016-08-30 16:57 ` Ronan Arraes Jardim Chagas
2016-08-31 20:49 ` Ronan Arraes Jardim Chagas
2016-08-31 21:44 ` Chris Murphy
2016-08-31 21:48 ` Chris Murphy
2016-08-31 22:47 ` Jeff Mahoney
2016-08-31 22:58 ` Chris Murphy
2016-08-31 23:03 ` Jeff Mahoney
2016-08-31 23:09 ` Chris Murphy
2016-09-01 12:57 ` Ronan Arraes Jardim Chagas
2016-09-01 13:21 ` Austin S. Hemmelgarn
2016-09-01 16:34 ` Ronan Arraes Jardim Chagas
2016-09-01 17:04 ` Austin S. Hemmelgarn
2016-09-01 17:12 ` Jeff Mahoney
2016-09-01 17:39 ` Ronan Arraes Jardim Chagas
2016-09-01 17:43 ` Jeff Mahoney
2016-09-01 17:58 ` Ronan Arraes Jardim Chagas
2016-09-01 17:45 ` Chris Murphy
2016-09-01 18:47 ` Austin S. Hemmelgarn
2016-09-02 0:12 ` Chris Murphy
2016-09-02 14:26 ` Jeff Mahoney
2016-09-02 14:43 ` Ronan Arraes Jardim Chagas
2016-09-02 14:48 ` Jeff Mahoney
2016-09-02 15:20 ` Ronan Arraes Jardim Chagas
2016-09-02 15:26 ` Jeff Mahoney
2016-09-02 19:25 ` Ronan Arraes Jardim Chagas
2016-09-05 8:49 ` Qu Wenruo
2016-09-08 18:24 ` Ronan Arraes Jardim Chagas
2016-09-08 18:49 ` Jeff Mahoney
2016-09-08 23:02 ` Jeff Mahoney
2016-09-13 20:24 ` Josef Bacik
2016-09-14 14:25 ` Jeff Mahoney
2016-09-19 2:38 ` Wang Xiaoguang
2016-09-22 13:40 ` Jeff Mahoney
[not found] ` <57DF4E44.2040506@cn.fujitsu.com>
2016-09-22 13:20 ` Ronan Arraes Jardim Chagas
2016-09-22 13:41 ` Austin S. Hemmelgarn
2016-09-22 14:03 ` Ronan Arraes Jardim Chagas
2016-09-22 14:39 ` Josef Bacik
2016-09-22 17:06 ` Ronan Arraes Jardim Chagas
2016-09-22 17:49 ` Josef Bacik
2016-09-22 17:54 ` Ronan Arraes Jardim Chagas
2016-09-23 15:20 ` [SOLVED] " Ronan Arraes Jardim Chagas
2016-09-02 19:56 ` Ronan Arraes Jardim Chagas [this message]
2016-09-02 21:34 ` Chris Murphy
2016-09-02 22:13 ` Ronan Arraes Jardim Chagas
2016-09-02 22:39 ` Chris Murphy
2016-09-03 2:47 ` Ronan Arraes Jardim Chagas
2016-09-03 3:41 ` Chris Murphy
2016-09-03 3:47 ` Ronan Arraes Jardim Chagas
2016-09-03 4:14 ` Chris Murphy
2016-09-01 17:07 ` Chris Murphy
2016-09-02 0:37 ` Qu Wenruo
2016-09-02 14:09 ` Jeff Mahoney
2016-09-14 20:15 ` Ronan Arraes Jardim Chagas
2016-09-14 22:25 ` Chris Murphy
2016-09-15 0:56 ` Ronan Arraes Jardim Chagas
2016-09-13 3:17 ` Wang Xiaoguang
2016-09-13 12:54 ` Ronan Arraes Jardim Chagas
2016-09-13 20:49 ` Ronan Arraes Jardim Chagas
2016-09-13 21:01 ` Josef Bacik
2016-09-14 14:40 ` Ronan Arraes Jardim Chagas
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=1472846181.13263.2.camel@gmail.com \
--to=ronisbr@gmail.com \
--cc=ahferroin7@gmail.com \
--cc=jeffm@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=quwenruo@cn.fujitsu.com \
--cc=wangxg.fnst@cn.fujitsu.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).