From: Konrad Rzeszutek <konrad@virtualiron.com>
To: Daniel Keisling <Daniel.Keisling@ppdi.com>
Cc: device-mapper development <dm-devel@redhat.com>
Subject: Re: RE: Temporarily squelching multipathd errors
Date: Mon, 19 Jan 2009 10:07:06 -0500 [thread overview]
Message-ID: <20090119150706.GA21668@mars.virtualiron.com> (raw)
In-Reply-To: <65F9ACC78BD8304BAAEB817634C62D4C0744141F@AUSMAIL01.americas.ppdi.local>
>
> I'm not in this test. Since all this takes around 20 seconds, I can
> immediately mount the LUN again on the server with any SCSI devices
> permanently disappearing.
>
> Would you like me to:
>
> A) Umount the filesystem
> B) Perform a 'dmsetup remove mpath33'
> C) Delete all SCSI devices via /sys/block/$device/delete
> D) Tell the storage unit to unpresent and delete the LUN
> E) Optionally do a SCSI rescan to clear everything out
> F) Tell the storage unit to create the LUN with the same WWID and SCSI
> ID
> G) Perform a SCSI rescan
> H) Do a multipath -v3 to get the maps back (?)
> I) Fsck and mount the filesystem?
>
> I believe I get the same results as what I pasted, but will prove it if
> need be.
Please do. Step B might be unnecessary as multipathd will figure out that
devices are gone (by step C) and start removing the block devices from the
map.
>
> BTW, I do a SCSI rescan with the HP Fibreutils package (hp_rescan -a),
> which basically does a "echo "- - -" >
> /sys/class/scsi_host/${INST}/scan" and removes devices with "echo "scsi
> remove-single-device $INST 0 $j $k" > /proc/scsi/scsi"
You only need to do the first step: echo "- - -" > /sys/class/scsi/host/hostX/scan
>
> Thanks,
>
> Daniel
>
> ______________________________________________________________________
> This email transmission and any documents, files or previous email
> messages attached to it may contain information that is confidential or
> legally privileged. If you are not the intended recipient or a person
> responsible for delivering this transmission to the intended recipient,
> you are hereby notified that you must not read this transmission and
> that any disclosure, copying, printing, distribution or use of this
> transmission is strictly prohibited. If you have received this transmission
> in error, please immediately notify the sender by telephone or return email
> and delete the original transmission and its attachments without reading
> or saving in any manner.
>
prev parent reply other threads:[~2009-01-19 15:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-19 8:27 Temporarily squelching multipathd errors Christophe Varoqui
2008-10-30 15:48 ` Daniel Keisling
2008-10-30 16:15 ` Domenico Viggiani
2008-11-21 19:54 ` Daniel Keisling
2008-11-26 17:43 ` Konrad Rzeszutek
2009-01-16 20:59 ` Daniel Keisling
[not found] ` <65F9ACC78BD8304BAAEB817634C62D4C07441224@AUSMAIL01.americas.ppdi.local>
2009-01-16 21:28 ` Konrad Rzeszutek
2009-01-16 21:52 ` Daniel Keisling
2009-01-19 15:07 ` Konrad Rzeszutek [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=20090119150706.GA21668@mars.virtualiron.com \
--to=konrad@virtualiron.com \
--cc=Daniel.Keisling@ppdi.com \
--cc=dm-devel@redhat.com \
/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