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: Thu, 20 Feb 2020 17:14:19 +0100 [thread overview]
Message-ID: <7376c09c-63e3-488f-fcf8-89c81832ef2d@dupond.be> (raw)
In-Reply-To: <20200220155022.GA532518@mit.edu>
On 20/02/2020 16:50, Theodore Y. Ts'o wrote:
> On Thu, Feb 20, 2020 at 10:08:44AM +0100, Jean-Louis Dupond wrote:
>> dumpe2fs -> see attachment
> Looking at the dumpe2fs output, it's interesting that it was "clean
> with errors", without any error information being logged in the
> superblock. What version of the kernel are you using? I'm guessing
> it's a fairly old one?
Debian 10 (Buster), with kernel 4.19.67-2+deb10u1
>> Fsck:
>> # e2fsck -fy /dev/mapper/vg01-root
>> e2fsck 1.44.5 (15-Dec-2018)
> And that's a old version of e2fsck as well. Is this some kind of
> stable/enterprise linux distro?
Debian 10 indeed.
>> Pass 1: Checking inodes, blocks, and sizes
>> Inodes that were part of a corrupted orphan linked list found. Fix? yes
>>
>> Inode 165708 was part of the orphaned inode list. FIXED.
> OK, this and the rest looks like it's relating to a file truncation or
> deletion at the time of the disconnection.
>
> > > > On KVM for example there is a unlimited timeout (afaik) until the
>>>> storage is
>>>> back, and the VM just continues running after storage recovery.
>>> Well, you can adjust the SCSI timeout, if you want to give that a try....
>> It has some other disadvantages? Or is it quite safe to increment the SCSI
>> timeout?
> It should be pretty safe.
>
> Can you reliably reproduce the problem by disconnecting the machine
> from the SAN?
Yep, can be reproduced by killing the connection to the SAN while the VM
is running, and then after the scsi timeout passed, re-enabled the SAN
connection.
Then reset the machine, and then you need to run an fsck to have it back
online.
> - Ted
next prev parent reply other threads:[~2020-02-20 16:14 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 [this message]
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
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=7376c09c-63e3-488f-fcf8-89c81832ef2d@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).