archive mirror
 help / color / mirror / Atom feed
Cc: Linux Kernel Mailing List <>,
Subject: Re: PROBLEM: IO lockup on reiserfs FS.
Date: Wed, 5 Aug 2020 20:01:29 -0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Wed, 5 Aug 2020 12:51:41 -0700
Linus Torvalds <> wrote:
> On Wed, Aug 5, 2020 at 9:53 AM <> wrote:
> >
> > It's been over 1 week since I sent this into the reiserfs-devel
> > mailing list. I'm escalating this as the kernel docs recommend.
> > I'm still willing to help debug and test a fix for this problem.  
> The thing is, you're using an ancient 4.14 kernel, 

Sorry, I didn't realize kernel development went that fast.
I did try to go to the 5.X series, but the AMDGPU drivers don't work on
my SI card anymore (I need to bisect which takes time and many re-boots
to find the problematic commit).
I'll try the Radeon-SI driver and see if I can reproduce this reliably.

> and a filesystem
> that isn't really maintained any more. You'll find very few people
> interested in trying to debug that combination.
> You *might* have more luck with a more modern kernel, but even then
> ... reiserfs?
>               Linus

Why does no one (I've met others who share a similar sentiment), like
reiserfs? I'm not looking for fight, I'm incredulous. It's a great FS
that survives oops-es, power failures, and random crashes very very well.
It's the only FLOSS FS with tail packing.


  reply	other threads:[~2020-08-06  0:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2020-07-29  2:34 ` PROBLEM: IO lockup on reiserfs FS David Niklas
2020-08-05 16:53   ` Hgntkwis
2020-08-05 19:51     ` Linus Torvalds
2020-08-06  0:01       ` Hgntkwis [this message]
2020-08-06  0:37         ` Edward Shishkin
2020-08-17 14:56       ` David Niklas
2020-09-24 17:21         ` PATCH reiser4 support for Linux 5.8.10 David Niklas
2020-09-24 18:34           ` Edward Shishkin
2020-09-24 19:14             ` David Niklas
2020-07-29  2:34 PROBLEM: IO lockup on reiserfs FS David Niklas
2020-08-06  2:05 Metztli Information Technology

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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).