On Wed, 2007-11-07 at 16:44 +0100, Domenico Viggiani wrote: > > -----Original Message----- > > From: dm-devel-bounces@xxxxxxxxxx > > [mailto:dm-devel-bounces@xxxxxxxxxx] On Behalf Of S. J. van Harmelen > > Sent: Wednesday, November 07, 2007 4:19 PM > > > > On Wed, 2007-11-07 at 08:33 -0500, Paul Cote wrote: > > > Did you do a rescan so that the O/S "sees" the new LUN? > > > > Nope... Could you tell me how to do that? And does a rescan > > have any effect on already active LUN's? > > # Send a LIP (loop initialization primitive) to the fabric 0 > echo "1" > /sys/class/fc_host/host0/issue_lip Thanks for you help. But the MD3000 has SAS HBA's, so I don't have the issue_lip file on my system. Any other way to get the same results for a SAS HBA? And once again... Does this interrupt the LUN's that are already attached and in use? Thanks!! > > # Scan SCSI bus 0: > echo "- - -" > /sys/class/scsi_host/host0/scan > > # Send a LIP (loop initialization primitive) to the fabric 1 > echo "1" > /sys/class/fc_host/host1/issue_lip > > # Scan SCSI bus 1: > echo "- - -" > /sys/class/scsi_host/host1/scan > > # sometime is needed to repeat above steps two times? > > # Check /var/log/messages and /proc/scsi/scsi > > # Create multipath > multipath -v2 > multipath -ll > > -- > dm-devel mailing list > dm-devel@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/dm-devel -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
