From: Marc Lehmann <schmorp@schmorp.de>
To: Remi Gauvin <remi@georgianit.com>
Cc: Qu Wenruo <quwenruo.btrfs@gmx.com>, linux-btrfs@vger.kernel.org
Subject: Re: btrfs dev del not transaction protected?
Date: Fri, 20 Dec 2019 19:00:19 +0100 [thread overview]
Message-ID: <20191220180018.GA6802@schmorp.de> (raw)
In-Reply-To: <45b11982-0847-8e2c-b40f-0c22ed21de2b@georgianit.com>
On Fri, Dec 20, 2019 at 12:24:05PM -0500, Remi Gauvin <remi@georgianit.com> wrote:
> You don't need hints, the problem is right here.
> Your Metadata is Raid 1, (which requires minimum of 2 devices,) Your
Guess I found another bug - three disks with >>3tb free space, but df
still shows 0 available bytes. Sure I can probably work around it somehow,
but no, I refuse to accept that this is supposedly a user problem - surely
btrfs could create more raid1 metadata with _three disks with lots of free
space_.
doom ~# df /cold1
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/xmnt-cold15 43T 23T 0 100% /cold1
doom ~# btrfs dev us /cold1
/dev/mapper/xmnt-cold15, ID: 1
Device size: 9.09TiB
Device slack: 0.00B
Data,single: 9.07TiB
Metadata,RAID1: 25.46GiB
System,RAID1: 32.00MiB
Unallocated: 1.00MiB
/dev/mapper/xmnt-cold12, ID: 2
Device size: 7.28TiB
Device slack: 0.00B
Data,single: 7.25TiB
Metadata,RAID1: 24.46GiB
System,RAID1: 32.00MiB
Unallocated: 1.00MiB
/dev/mapper/xmnt-cold13, ID: 3
Device size: 7.28TiB
Device slack: 0.00B
Data,single: 4.03TiB
Metadata,RAID1: 5.92GiB
Unallocated: 3.24TiB
/dev/mapper/xmnt-cold14, ID: 4
Device size: 7.28TiB
Device slack: 0.00B
Unallocated: 7.28TiB
/dev/mapper/xmnt-cold11, ID: 5
Device size: 7.28TiB
Device slack: 0.00B
Unallocated: 7.28TiB
--
The choice of a Deliantra, the free code+content MORPG
-----==- _GNU_ http://www.deliantra.net
----==-- _ generation
---==---(_)__ __ ____ __ Marc Lehmann
--==---/ / _ \/ // /\ \/ / schmorp@schmorp.de
-=====/_/_//_/\_,_/ /_/\_\
next prev parent reply other threads:[~2019-12-20 18:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-20 4:05 btrfs dev del not transaction protected? Marc Lehmann
2019-12-20 5:24 ` Qu Wenruo
2019-12-20 6:37 ` Marc Lehmann
2019-12-20 7:10 ` Qu Wenruo
2019-12-20 13:27 ` Marc Lehmann
2019-12-20 13:41 ` Qu Wenruo
2019-12-20 16:53 ` Marc Lehmann
2019-12-20 17:24 ` Remi Gauvin
2019-12-20 17:50 ` Marc Lehmann
2019-12-20 18:00 ` Marc Lehmann [this message]
2019-12-20 18:28 ` Eli V
2019-12-20 20:24 ` Chris Murphy
2019-12-20 23:30 ` Marc Lehmann
2019-12-21 20:06 ` Zygo Blaxell
2019-12-21 1:32 ` Qu Wenruo
2019-12-20 17:07 ` Marc Lehmann
2019-12-21 1:23 ` Qu Wenruo
2019-12-20 17:20 ` Marc Lehmann
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=20191220180018.GA6802@schmorp.de \
--to=schmorp@schmorp.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
--cc=remi@georgianit.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