From: torn5 <torn5@shiftmail.org>
To: linux-ext4@vger.kernel.org,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Ext4 and scsi commands resubmission
Date: Tue, 28 Dec 2010 11:41:58 +0100 [thread overview]
Message-ID: <4D19BEF6.5010007@shiftmail.org> (raw)
Hello all,
in open-iscsi, when network connectivity is lost, scsi commands that
were in-flight at the moment of disconnection are failed to the SCSI layer.
These get resubmitted up to 5 times by the SCSI layer (or so is written
in the open-iscsi docs) and after that they are held in the queue
(device "blocked") until the network connection is restored.
Now the question is: when SCSI resubmits commands to a device, I suppose
they go to the end of the queue for the device, and not at the head like
they were. Am I right?
How do filesystems, and in particular ext4, react to that?
I suppose the ordering goes awry, barriers cannot succeed in this way,
especially if they were submitted as real SCSI barriers (i.e. without
using flush + command + flush workaround)
Thank you
next reply other threads:[~2010-12-28 10:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-28 10:41 torn5 [this message]
2010-12-29 4:43 ` Ext4 and scsi commands resubmission Mike Christie
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=4D19BEF6.5010007@shiftmail.org \
--to=torn5@shiftmail.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-scsi@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 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).