All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Jones <paul@pauljones.id.au>
To: Zygo Blaxell <ce3g8jdj@umail.furryterror.org>,
	Asif Youssuff <yoasif@gmail.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: RE: Filesystem goes readonly soon after mount, cannot free space or rebalance
Date: Wed, 23 Jun 2021 06:08:58 +0000	[thread overview]
Message-ID: <SYXPR01MB191839844E7C773F755E110B9E089@SYXPR01MB1918.ausprd01.prod.outlook.com> (raw)
In-Reply-To: <20210623053240.GJ11733@hungrycats.org>

> -----Original Message-----
> From: Zygo Blaxell <ce3g8jdj@umail.furryterror.org>
> Sent: Wednesday, 23 June 2021 3:33 PM
> To: Asif Youssuff <yoasif@gmail.com>
> Cc: linux-btrfs@vger.kernel.org
> Subject: Re: Filesystem goes readonly soon after mount, cannot free space
> or rebalance
>  
> You might be able to recover by booting a kernel with a patch to delay
> startup of the btrfs-cleaner thread, thereby preventing the snapshot
> delete from restarting immediately and breaking the filesystem.  I haven't
> tried it, but it was my plan B if reverting to 4.19 hadn't worked.

Yes, I had to do that and it worked nicely. I don't remember the details, but I just commented out the part that forced a RO remount. The cleaner thread would still run and fail, but at least I could add two drives to my raid array for long enough to fix the problem.


Paul.

  reply	other threads:[~2021-06-23  6:09 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
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 [this message]
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=SYXPR01MB191839844E7C773F755E110B9E089@SYXPR01MB1918.ausprd01.prod.outlook.com \
    --to=paul@pauljones.id.au \
    --cc=ce3g8jdj@umail.furryterror.org \
    --cc=linux-btrfs@vger.kernel.org \
    --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.