From: Christoph Hellwig <hch@infradead.org>
To: Albert Duato <albert@kumori.systems>
Cc: Christoph Hellwig <hch@infradead.org>,
"linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>
Subject: Re: How to avoid xfs_do_force_shutdown on xlog_iodone error
Date: Mon, 3 Dec 2018 01:10:52 -0800 [thread overview]
Message-ID: <20181203091052.GA26446@infradead.org> (raw)
In-Reply-To: <VI1P192MB02881322EC7B4A0624515B01A9AE0@VI1P192MB0288.EURP192.PROD.OUTLOOK.COM>
On Mon, Dec 03, 2018 at 09:08:40AM +0000, Albert Duato wrote:
> Thanks.
>
> I didn't know about that command, but after reading its man and trying it,
> it seems to require to freeze the XFS before a disconnection, and that's
> nothing that could be predicted.
>
> I should have said it on the initial mail, that the temporary disconnections
> are not scheduled, but arbitrary, as they depend on network availability.
>
> As long as all operations were retried, network gaps would only cause
> delays, but not fatal failures.
>
> Is that something I can configure?
No, you can't. The only think you can do is to make sure I/Os
don't get completed on a disconnect. Other protocols like SCSI or NBD
at usually try to reconnect and only fail the I/O if that fails. You'd
either have to fix that in nbd, or try some nasty workarounds like
creating a dm-multipath device with a single path on top of you nbd
device and set the queue_if_no_path option.
prev parent reply other threads:[~2018-12-03 9:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <VI1P192MB0288B67B92CE171B34ABBB1AA9D30@VI1P192MB0288.EURP192.PROD.OUTLOOK.COM>
2018-11-30 11:59 ` How to avoid xfs_do_force_shutdown on xlog_iodone error Albert Duato
2018-12-02 16:08 ` Christoph Hellwig
2018-12-03 9:08 ` Albert Duato
2018-12-03 9:10 ` Christoph Hellwig [this message]
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=20181203091052.GA26446@infradead.org \
--to=hch@infradead.org \
--cc=albert@kumori.systems \
--cc=linux-xfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.