From: Chris Murphy <lists@colorremedies.com>
To: Asif Youssuff <yoasif@gmail.com>
Cc: Qu Wenruo <quwenruo.btrfs@gmx.com>, Qu Wenruo <wqu@suse.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Filesystem goes readonly soon after mount, cannot free space or rebalance
Date: Tue, 22 Jun 2021 15:33:22 -0600 [thread overview]
Message-ID: <CAJCQCtTW0tR-55UkkE=r0ONQucCO7_An2ASOQeBjZiZXtPrLSg@mail.gmail.com> (raw)
In-Reply-To: <CAHw5_hm+UX2EHSdZHcMXWMNYxOtccKMQ1qtfbu1gKUm-WZFXYg@mail.gmail.com>
On Tue, Jun 22, 2021 at 12:37 AM Asif Youssuff <yoasif@gmail.com> wrote:
> I went ahead and also created two partitions each on the two new usb
> disks (for a two of four new partitions) and added them to the btrfs
> filesystem using "btrfs device add", then removing a snapshot followed
> by a "btrfs fi sync". The filesystem still goes ro after a while.
Yeah Qu is correct, and I had it wrong. Two devices have enough space
for a new metadata BG, but no other disks. And it requires four. All
you need is to add two but it won't even let you add one before it
goes ro. So it's stuck. Until there is a kernel fix for this, it's
permanently read-only (unless we're missing some other work around).
> Would mounting as degraded make it possible to add the disks and have
> it stick?
No, that's even more fragile and you're sure to run into myriad
degraded raid5 bugs, not least of which are the bogus errors. And it
won't be obvious which ones are important and which ones are not.
--
Chris Murphy
next prev parent reply other threads:[~2021-06-22 21:33 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-19 5:16 Filesystem goes readonly soon after mount, cannot free space or rebalance Asif Youssuff
2021-06-19 18:47 ` Chris Murphy
2021-06-20 9:11 ` Asif Youssuff
[not found] ` <ab0e8705-e18f-90eb-c42b-318c04a2101c@gmail.com>
2021-06-20 16:24 ` Chris Murphy
2021-06-20 16:49 ` Chris Murphy
2021-06-21 2:04 ` Asif Youssuff
2021-06-21 3:27 ` Chris Murphy
2021-06-21 6:53 ` Asif Youssuff
2021-06-21 7:42 ` Qu Wenruo
2021-06-21 23:14 ` Asif Youssuff
2021-06-21 23:36 ` Qu Wenruo
2021-06-22 0:12 ` Asif Youssuff
2021-06-22 0:25 ` Qu Wenruo
2021-06-22 0:50 ` Asif Youssuff
2021-06-22 0:55 ` Asif Youssuff
2021-06-22 3:15 ` Qu Wenruo
2021-06-22 4:54 ` Asif Youssuff
2021-06-22 5:03 ` Qu Wenruo
2021-06-22 6:37 ` Asif Youssuff
2021-06-22 21:33 ` Chris Murphy [this message]
2021-06-23 9:32 ` Asif Youssuff
2021-06-23 9:37 ` Qu Wenruo
2021-06-23 9:53 ` Forza
2021-06-23 16:24 ` Asif Youssuff
2021-06-23 16:29 ` Martin Raiber
2021-07-27 21:58 ` Asif Youssuff
2021-06-23 5:32 ` Zygo Blaxell
2021-06-23 6:08 ` Paul Jones
2021-06-23 9:22 ` Asif Youssuff
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='CAJCQCtTW0tR-55UkkE=r0ONQucCO7_An2ASOQeBjZiZXtPrLSg@mail.gmail.com' \
--to=lists@colorremedies.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
--cc=wqu@suse.com \
--cc=yoasif@gmail.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.