From: Jean-Louis Dupond <jean-louis@dupond.be>
To: "Theodore Y. Ts'o" <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Filesystem corruption after unreachable storage
Date: Fri, 28 Feb 2020 12:06:17 +0100 [thread overview]
Message-ID: <d19e44af-585f-e4a2-5546-7a3345a0ee66@dupond.be> (raw)
In-Reply-To: <20200225172355.GA14617@mit.edu>
On 25/02/2020 18:23, Theodore Y. Ts'o wrote:
> On Tue, Feb 25, 2020 at 02:19:09PM +0100, Jean-Louis Dupond wrote:
>> FYI,
>>
>> Just did same test with e2fsprogs 1.45.5 (from buster backports) and kernel
>> 5.4.13-1~bpo10+1.
>> And having exactly the same issue.
>> The VM needs a manual fsck after storage outage.
>>
>> Don't know if its useful to test with 5.5 or 5.6?
>> But it seems like the issue still exists.
> This is going to be a long shot, but if you could try testing with
> 5.6-rc3, or with this commit cherry-picked into a 5.4 or later kernel:
>
> commit 8eedabfd66b68a4623beec0789eac54b8c9d0fb6
> Author: wangyan <wangyan122@huawei.com>
> Date: Thu Feb 20 21:46:14 2020 +0800
>
> jbd2: fix ocfs2 corrupt when clearing block group bits
>
> I found a NULL pointer dereference in ocfs2_block_group_clear_bits().
> The running environment:
> kernel version: 4.19
> A cluster with two nodes, 5 luns mounted on two nodes, and do some
> file operations like dd/fallocate/truncate/rm on every lun with storage
> network disconnection.
>
> The fallocate operation on dm-23-45 caused an null pointer dereference.
> ...
>
> ... it would be interesting to see if fixes things for you. I can't
> guarantee that it will, but the trigger of the failure which wangyan
> found is very similar indeed.
>
> Thanks,
>
> - Ted
Unfortunately it was a too long shot :)
Tested with a 5.4 kernel with that patch included, and also with 5.6-rc3.
But both had the same issue.
- Filesystem goes read-only when the storage comes back
- Manual fsck needed on bootup to recover from it.
It would be great if we could make it not corrupt the filesystem on
storage recovery.
I'm happy to test some patches if they are available :)
Thanks
Jean-Louis
next prev parent reply other threads:[~2020-02-28 11:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-24 10:57 Filesystem corruption after unreachable storage Jean-Louis Dupond
2020-01-24 20:37 ` Theodore Y. Ts'o
2020-02-20 9:08 ` Jean-Louis Dupond
2020-02-20 9:14 ` Jean-Louis Dupond
2020-02-20 15:50 ` Theodore Y. Ts'o
2020-02-20 16:14 ` Jean-Louis Dupond
2020-02-25 13:19 ` Jean-Louis Dupond
2020-02-25 17:23 ` Theodore Y. Ts'o
2020-02-28 11:06 ` Jean-Louis Dupond [this message]
2020-03-09 13:52 ` Jean-Louis Dupond
2020-03-09 15:18 ` Theodore Y. Ts'o
2020-03-09 15:33 ` Jean-Louis Dupond
2020-03-09 22:32 ` Theodore Y. Ts'o
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=d19e44af-585f-e4a2-5546-7a3345a0ee66@dupond.be \
--to=jean-louis@dupond.be \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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).