From: Josef Bacik <jbacik@fb.com>
To: Ronan Arraes Jardim Chagas <ronisbr@gmail.com>,
"Austin S. Hemmelgarn" <ahferroin7@gmail.com>,
Wang Xiaoguang <wangxg.fnst@cn.fujitsu.com>,
"Jeff Mahoney" <jeffm@suse.com>,
Qu Wenruo <quwenruo@cn.fujitsu.com>,
Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: BTRFS constantly reports "No space left on device" even with a huge unallocated space
Date: Thu, 22 Sep 2016 13:49:54 -0400 [thread overview]
Message-ID: <949294ac-fe4a-10b1-70aa-e9a65530d0d5@fb.com> (raw)
In-Reply-To: <1474563967.3206.16.camel@gmail.com>
On 09/22/2016 01:06 PM, Ronan Arraes Jardim Chagas wrote:
> Hi Josef,
>
> Em qui, 2016-09-22 às 10:39 -0400, Josef Bacik escreveu:
>> This is what fixed it. I thought it was in 4.7 which is why I
>> started paying
>> attention, but I guess I was wrong. Glad your problem is
>> resolved. Thanks,
>
> Do you have any explanations why the problem solved by the patch was
> causing me the ENOSPC? Also, is it necessary to format my partition or
> should I consider it good for use after the installation of the new
> kernel?
That patch fixed a problem where we would screw up the ENOSPC accounting, and
would slowly leak space into one of the counters. So eventually (or often in
your case) you'd hit ENOSPC, but have plenty of space available. If you
unmounted and mounted again, or simply rebooted, everything would have been
fine. You can still use the fs, the accounting is purely in memory so it's not
like your FS is permanently screwed. Thanks,
Josef
next prev parent reply other threads:[~2016-09-22 17:50 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 [this message]
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
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=949294ac-fe4a-10b1-70aa-e9a65530d0d5@fb.com \
--to=jbacik@fb.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=ronisbr@gmail.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 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.