From: Linus Torvalds <torvalds@linux-foundation.org>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: linux-bcachefs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] bcachefs fixes for 6.16-rc3
Date: Thu, 19 Jun 2025 17:51:17 -0700 [thread overview]
Message-ID: <CAHk-=wi2ae794_MyuW1XJAR64RDkDLUsRHvSemuWAkO6T45=YA@mail.gmail.com> (raw)
In-Reply-To: <4xkggoquxqprvphz2hwnir7nnuygeybf2xzpr5a4qtj4cko6fk@dlrov4usdlzm>
On Thu, 19 Jun 2025 at 16:06, Kent Overstreet <kent.overstreet@linux.dev> wrote:
>
> - New option: journal_rewind
>
> This lets the entire filesystem be reset to an earlier point in time.
>
> Note that this is only a disaster recovery tool, and right now there
> are major caveats to using it (discards should be disabled, in
> particular), but it successfully restored the filesystem of one of the
> users who was bit by the subvolume deletion bug and didn't have
> backups. I'll likely be making some changes to the discard path in the
> future to make this a reliable recovery tool.
You seem to have forgotten what the point of the merge window was again.
We don't start adding new features just because you found other bugs.
I remain steadfastly convinced that anybody who uses bcachefs is
expecting it to be experimental. They had better.
Make the -rc fixes be pure fixes.
Linus
next prev parent reply other threads:[~2025-06-20 0:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-19 23:06 [GIT PULL] bcachefs fixes for 6.16-rc3 Kent Overstreet
2025-06-20 0:51 ` Linus Torvalds [this message]
2025-06-20 1:09 ` Kent Overstreet
2025-06-20 1:25 ` Jani Partanen
2025-06-20 1:51 ` Kent Overstreet
2025-06-20 7:12 ` Martin Steigerwald
2025-06-20 7:27 ` Martin Steigerwald
2025-06-20 8:14 ` Kent Overstreet
2025-06-20 12:43 ` Theodore Ts'o
2025-06-20 15:17 ` Christoph Heinrich
2025-06-20 23:34 ` Kent Overstreet
2025-06-21 0:15 ` Kent Overstreet
2025-06-21 21:07 ` Jérôme Poulin
2025-06-21 22:50 ` Jérôme Poulin
2025-06-21 23:46 ` Kent Overstreet
2025-06-27 3:33 ` pr-tracker-bot
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='CAHk-=wi2ae794_MyuW1XJAR64RDkDLUsRHvSemuWAkO6T45=YA@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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).