[Bug 1135453] Re: open-iscsi +mpio with multipathd init script order errors
** Changed in: multipath-tools (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1135453 Title: open-iscsi +mpio with multipathd init script order errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1135453/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1135453] Re: open-iscsi +mpio with multipathd init script order errors
** Changed in: multipath-tools (Ubuntu) Assignee: (unassigned) = Peter Petrakis (peter-petrakis) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1135453 Title: open-iscsi +mpio with multipathd init script order errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1135453/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1135453] Re: open-iscsi +mpio with multipathd init script order errors
This might be self inflicted. First, we have really good multipath documentation now. You're better off following our docs first and then supplementing it with the vendor docs if it doesn't work. Many popular SANs have built-in support. https://help.ubuntu.com/12.04/serverguide/dm-multipath-chapter.html HP MSA's are already included in the built-in DB, your config file is likely not needed so lets start by eliminating that as a variable by following these directions. https://help.ubuntu.com/12.04/serverguide/multipath-setting-up-dm- multipath.html#multipath-setup-overview plus your path alias, and, # update-initramfs -u -k all To copy the multipath.conf to the ramdisk. Make all these changes, reboot, and before you shutdown again grab: * sudo dmsetup table * sudo udisks --dump * sudo -i; echo 'show config' | multipathd -k and attach to the bug. Thanks. I'm hoping you have a newer MSA and this is just a mp jumbled config. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1135453 Title: open-iscsi +mpio with multipathd init script order errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1135453/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1135453] Re: open-iscsi +mpio with multipathd init script order errors
if i remember correctly, i made the config from the HP MSA
recommendations for multipathd.conf
here my multipathd.conf config:
defaults {
udev_dir/dev
polling_interval30
selectorround-robin 0
path_grouping_policymultibus
getuid_callout /lib/udev/scsi_id --whitelisted --device=/dev/%n
prio_callout/bin/true
path_checkerreadsector0
prioconst
rr_min_io 100
rr_weight uniform
failbackimmediate
no_path_retry 12
user_friendly_name yes
hardware_handler0
}
blacklist {
devnode sda
devnode ^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*
devnode ^hd[a-z][[0-9]*]
devnode ^vd[a-z]
devnode ^cciss!c[0-9]d[0-9]*[p[0-9]*]
}
multipaths {
multipath {
wwid mypseudorandomwwid901243012701704
alias mydevname
}
}
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1135453
Title:
open-iscsi +mpio with multipathd init script order errors
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1135453/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1135453] Re: open-iscsi +mpio with multipathd init script order errors
here my iscsi config dir from /etc ** Attachment added: iscsi configuration from /etc on affected host https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1135453/+attachment/3552742/+files/iscsicfg.gz -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1135453 Title: open-iscsi +mpio with multipathd init script order errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1135453/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1135453] Re: open-iscsi +mpio with multipathd init script order errors
On Friday 01 March 2013 05:49 PM, Mike Burgener wrote:
defaults {
udev_dir/dev
polling_interval30
selectorround-robin 0
path_grouping_policymultibus
getuid_callout /lib/udev/scsi_id --whitelisted --device=/dev/%n
prio_callout/bin/true
path_checkerreadsector0
prioconst
rr_min_io 100
rr_weight uniform
failbackimmediate
no_path_retry 12
user_friendly_name yes
hardware_handler0
}
The behavior you reported is pretty interesting. You reported that you
suffered the hang state because the umount occurred after the multipathd
and iscsid processes were killed by the init scripts (which I also
assumed given the new init systems, upstart and systemd).
But looking at your config, you should not typically see the hang
scenario. I was suspecting that you might be using the multipath
queue_if_no_path feature, but that is not the case here. The iscsi
replacement timeouts are also the defaults, i.e. 120 seconds, which
would mean that after 120 seconds of retry, iscsi will error out and the
errors will propagate to the upper layers.
Ideally, with the configuration settings that you have, you should see
the errors show up after 120 seconds, and NOT hang. I have no more ideas
on what might be going wrong in your setup. Perhaps the Ubuntu multipath
maintainer might have some insight to this.
--
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
Necessity is the mother of invention.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1135453
Title:
open-iscsi +mpio with multipathd init script order errors
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1135453/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1135453] Re: open-iscsi +mpio with multipathd init script order errors
you seem to feel that it is normal that multipathd is stopped then the iscsi device logged out (so the blockdevice disappears) and then umount? this would end in a possible dataloss scenario isn't it? btw. also bootup does not work so there must be some logical error i think. of course the 120 hung timeout message from kernel arrives but i think it does never continue as it can no more sync disks? could that make sense? regards Mike -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1135453 Title: open-iscsi +mpio with multipathd init script order errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1135453/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1135453] Re: open-iscsi +mpio with multipathd init script order errors
On Fri, Mar 1, 2013 at 11:08 PM, Mike Burgener mburge...@tuxinator.orgwrote: you seem to feel that it is normal that multipathd is stopped then the iscsi device logged out (so the blockdevice disappears) and then umount? No. The correct steps are to first umount the device, then flush the multipath map, and then depending on the transport (iSCSI, FC or FCoE) act further. Never should we do it any other way. It is just asking for too much trouble. But technically iscsid or multipatd daemon processes are not the core performers. If you look at my Debian packages regular system v init scripts, you'll see that killing the daemon and terminating the iscsi sessions are 2 different tasks [1]. That's what I meant in my previous mails. [1] http://anonscm.debian.org/gitweb/?p=pkg-iscsi/open-iscsi.git;a=blob;f=debian/open-iscsi.init;h=221fc9147f684bdb0bbcbda36799d5867bc617f2;hb=HEAD this would end in a possible dataloss scenario isn't it? Hard to predict. But yes, there could be a rare chance. btw. also bootup does not work so there must be some logical error i think. Would it be possible for you to test this out on a sysv init? Or maybe even try this on Debian? (But do note that the Ubuntu packages are not directly identical to Debian ones). of course the 120 hung timeout message from kernel arrives but i think it does never continue as it can no more sync disks? could that make sense? That might be the hung_task kernel messages. Yes. regards Mike -- You received this bug notification because you are subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1135453 Title: open-iscsi +mpio with multipathd init script order errors Status in “multipath-tools” package in Ubuntu: New Bug description: when using open-iscsi and multipathd for a mpio setup there are several init script logical issues: when shutting down, the system does first stop multipathd and then try to umount the filesystem and then stop open-iscsi to the system hangs forever on shutdown. also when booting up it does mount the partition before multipathd and open-iscsi are ready and you get the ubuntu screen that the partition could not get mounted, do you want to skip. after bootup process you can however mount the partition without any issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1135453/+subscriptions -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com Necessity is the mother of invention. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1135453 Title: open-iscsi +mpio with multipathd init script order errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1135453/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1135453] Re: open-iscsi +mpio with multipathd init script order errors
** Package changed: ubuntu = multipath-tools (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1135453 Title: open-iscsi +mpio with multipathd init script order errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1135453/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
