Linux XFS filesystem development
 help / color / mirror / Atom feed
From: Luis Chamberlain <mcgrof@kernel.org>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: linux-xfs@vger.kernel.org
Subject: Re: Unmountable XFS file system after runnig stress-ng
Date: Sat, 27 Jul 2019 00:24:39 +0000	[thread overview]
Message-ID: <20190727002439.GS30113@42.do-not-panic.com> (raw)
In-Reply-To: <b92674c4-488e-15ec-2052-eb69e4f80b7e@molgen.mpg.de>

On Thu, Jul 25, 2019 at 07:21:43PM +0200, Paul Menzel wrote:
> Dear Linux folks,

Hey Paul, thanks for reporting this!

> With Linux 4.19.57

v4.19.57 lacks a series of fixes I posted a few days ago.
They were merged on v4.19.61. You can try that. If that fails
another small series of fixes were posted recently which are
not merged yet ons table v4.19.y, but you can use this git
branch:

https://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux-stable.git/log/?h=20190726-linux-xfs-4.19.y-v1

> I ran `sudo ./stress-ng -a 10` [1], and it looks like the
> file system got corrupted.

Which version of  stress-ng did you use?

Can you try also on the latest Linus' tree?
If brave enough, you can try the xfs for-next branch
as well:

https://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git/log/?h=for-next

If the issue is still creeping up on the above stable kernels
can you create a bug entry on bugzilla.kernel.org to track this?

  Luis

  reply	other threads:[~2019-07-27  0:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-25 17:21 Unmountable XFS file system after runnig stress-ng Paul Menzel
2019-07-27  0:24 ` Luis Chamberlain [this message]
     [not found]   ` <CA+VdTb8ZPLi0Eiq9SEhem4aEjWJ3rCn+NQ_vZrpc9mXo_WuDDQ@mail.gmail.com>
2019-07-27 21:39     ` Paul Menzel

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=20190727002439.GS30113@42.do-not-panic.com \
    --to=mcgrof@kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=pmenzel@molgen.mpg.de \
    /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