From: "Cédric Lemarchand" <cedric.lemarchand@tdf.fr>
To: stgt@vger.kernel.org
Subject: ext4 corruption with MPIO and path_grouping_policy "multibus"
Date: Mon, 15 Jan 2018 18:55:00 +0100 [thread overview]
Message-ID: <63aea0d2-ac82-914d-6abd-10a20538646b@tdf.fr> (raw)
Hello,
One initiator is accessing 2 TGT instances on 2 hosts where the same
block device is shared among them (actually an RBD volume). The
configuration is as follow:
TGT1:
<target iqn.2017-08.storage:rbd0-1>
direct-store /dev/rbd0
write-cache off
</target>
TGT2:
<target iqn.2017-08.storage:rbd0-2>
direct-store /dev/rbd0
write-cache off
</target>
On the initiator, when multipath is configured with
'path_grouping_policy "multibus"' and formated in ext4, the fsck fails
systematically. The output of "multipath -ll" in the MP device :
360000000000000000e00000000010001 dm-17 IET,VIRTUAL-DISK
size=93G features='1 retain_attached_hw_handler' hwhandler='0' wp=rw
`-+- policy='service-time 0' prio=1 status=active
|- 11:0:0:1 sds 65:32 active ready running
`- 12:0:0:1 sdt 65:48 active ready running
I not some errors when tgt start :
read capacity (16): pass through os error: Inappropriate ioctl for device
READ CAPACITY (16) failed: Sense category: -1, try '-v' option for more
information
I cannot reproduce this issue with 'path_grouping_policy "failover"',
nor whit LIO as iSCSI target and 'path_grouping_policy "multibus"'. On
TGT hosts, the rbd cache is disabled ("rbd cache = false").
Did I miss something ? Any enlightenment in order to debug further will
be welcomed.
Debian Stretch
kernel 4.9.65
tgtd 1.0.69
multipath-tools 0.6.4
open-iscsi 2.0-874
next reply other threads:[~2018-01-15 17:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-15 17:55 Cédric Lemarchand [this message]
2018-01-17 15:08 ` ext4 corruption with MPIO and path_grouping_policy "multibus" Cédric Lemarchand
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=63aea0d2-ac82-914d-6abd-10a20538646b@tdf.fr \
--to=cedric.lemarchand@tdf.fr \
--cc=stgt@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 read-only IMAP folder(s) and NNTP newsgroup(s).