All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Lai <m@matthewlai.ca>
To: Nikolay Borisov <nborisov@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: Filesystem full with unallocated space?
Date: Thu, 19 Apr 2018 12:12:07 +0100	[thread overview]
Message-ID: <9c33b8be-f2f0-2b5d-856c-46acba79f0d7@matthewlai.ca> (raw)
In-Reply-To: <aa9580ac-eba2-038c-1e60-a57a05eb544d@suse.com>

Hi Nikolay,

Updating to 4.15 seems to have fixed it.

Thanks!

Matthew


On 04/18/2018 05:48 PM, Nikolay Borisov wrote:
>
> On 17.04.2018 19:08, Matthew Lai wrote:
>> Hello!
>>
>> I am getting ENOSPC on my root filesystem with plenty of unallocated
>> space according to "fi usage". Any idea why that may be? This is a root
>> partition for Debian Stable. Not doing anything unusual that I'm aware
>> of. No snapshots.
>>
>> Thanks!
>>
>> Matthew
>>
>> uname -a:
>> Linux bigfoot 4.9.0-4-amd64 #1 SMP Debian 4.9.65-3+deb9u1 (2017-12-23)
>> x86_64 GNU/Linux
>>
>> btrfs --version:
>> btrfs-progs v4.7.3
>>
>> btrfs fi show:
>> Label: none  uuid: 2364c63f-e20c-410f-90b4-05f722ee1c77
>>      Total devices 1 FS bytes used 176.27GiB
>>      devid    1 size 246.33GiB used 185.01GiB path /dev/sda2
>>
>> btrfs fi df /:
>> Data, single: total=183.00GiB, used=175.78GiB
>> System, single: total=4.00MiB, used=48.00KiB
>> Metadata, single: total=2.01GiB, used=504.81MiB
>> GlobalReserve, single: total=211.39MiB, used=0.00B
>>
>
> You haven't shown "btrfs fi usage". In any case there were some patches
> in more recent kernels which deal with premature ENOSPC:
>
>
> 996478ca9c46 ("btrfs: change how we decide to commit transactions during
> flushing")
> 17024ad0a0fd ("Btrfs: fix early ENOSPC due to delalloc")
>
>
> I'd advise you update to 4.14 stable. Otherwise running:
> git log --oneline --grep "enospc" fs/btrfs/
>
> will shows you likely candidates.


      reply	other threads:[~2018-04-19 11:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <89d90bb8-dbe3-1789-60eb-a29f9d1e3a64@matthewlai.ca>
2018-04-17 16:08 ` Filesystem full with unallocated space? Matthew Lai
2018-04-18 16:48   ` Nikolay Borisov
2018-04-19 11:12     ` Matthew Lai [this message]

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=9c33b8be-f2f0-2b5d-856c-46acba79f0d7@matthewlai.ca \
    --to=m@matthewlai.ca \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=nborisov@suse.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.