linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>
To: "dsterba@suse.cz" <dsterba@suse.cz>, Jingyun He <jingyun.ho@gmail.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: unable to use all spaces
Date: Fri, 17 Dec 2021 07:50:42 +0000	[thread overview]
Message-ID: <PH0PR04MB741690A2CA03A27CABCA7A139B789@PH0PR04MB7416.namprd04.prod.outlook.com> (raw)
In-Reply-To: 20211215155059.GB28560@twin.jikos.cz

On 15/12/2021 16:51, David Sterba wrote:
> On Wed, Dec 15, 2021 at 10:31:13PM +0800, Jingyun He wrote:
>> Hello,
>> I have a 14TB WDC HM-SMR disk formatted with BTRFS,
>> It looks like I'm unable to fill the disk full.
>> E.g. btrfs fi usage /disk1/
>> Free (estimated): 128.95GiB (min: 128.95GiB)
>>
>> It still has 100+GB available
>> But I'm unable to put more files.
> 
> We'd need more information to diagnose that, eg. output of 'btrfs fi df'
> to see if eg. the metadata space is not exhausted or if the remaining
> 128G account for the unusable space in the zones (this is also in the
> 'fi df' output).
Can 

  parent reply	other threads:[~2021-12-17  7:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-15 14:31 unable to use all spaces Jingyun He
2021-12-15 15:50 ` David Sterba
2021-12-15 23:58   ` Qu Wenruo
2021-12-21  3:38     ` Zygo Blaxell
2021-12-21  4:45       ` Qu Wenruo
2021-12-17  7:50   ` Johannes Thumshirn [this message]
2021-12-17  7:51   ` Johannes Thumshirn
2021-12-17 17:57     ` Jingyun He
2021-12-17 18:00       ` Jingyun He
2021-12-19 18:04         ` Jingyun He
2021-12-20  3:06           ` Jingyun He

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=PH0PR04MB741690A2CA03A27CABCA7A139B789@PH0PR04MB7416.namprd04.prod.outlook.com \
    --to=johannes.thumshirn@wdc.com \
    --cc=dsterba@suse.cz \
    --cc=jingyun.ho@gmail.com \
    --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 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).