From: Andrei Borzenkov <arvidjaar@gmail.com>
To: Cedric.dewijs@eclipso.eu, linux-btrfs@vger.kernel.org
Subject: Re: should btrfs reserve some space for root, so a normal user can't cause "no space left" problems?
Date: Fri, 8 Jan 2021 12:46:42 +0300 [thread overview]
Message-ID: <13fe8169-2740-95ca-09ca-efe0391dde4c@gmail.com> (raw)
In-Reply-To: <e0efe804fd52b0838bf69b01f6e7a784@mail.eclipso.de>
08.01.2021 10:56, Cedric.dewijs@eclipso.eu пишет:
> I have done a test where I filled up an entire btrfs raid 1 filesystem as a normal user. Then I simulated a failing drive. it turned out I was unable to replace the drive, as raid1 need free space on both drives. See this mail for details [1]
As explained in this mail, you did not "replace" drive, you added new
drive. This is different operation.
>
> I can understand the technical reasoning behind the requirement of both drives having some free space. But why does btrfs by default allow a normal, non root user to completely fill up the drive? Maybe it's a good idea to reserve some blocks on the filesystem that are only available for the root user, much like ext4 does that (via tune2fs [-m reserved_blocks_percent] and [-r reserved_blocks_count])
>
> [1] https://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg92550.html
>
> ---
>
> Take your mailboxes with you. Free, fast and secure Mail & Cloud: https://www.eclipso.eu - Time to change!
>
>
prev parent reply other threads:[~2021-01-08 9:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-08 7:56 should btrfs reserve some space for root, so a normal user can't cause "no space left" problems?
2021-01-08 9:46 ` Andrei Borzenkov [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=13fe8169-2740-95ca-09ca-efe0391dde4c@gmail.com \
--to=arvidjaar@gmail.com \
--cc=Cedric.dewijs@eclipso.eu \
--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