From mboxrd@z Thu Jan 1 00:00:00 1970 From: Oren Held Subject: Re: Rescan for new LUNs Date: Thu, 01 Jul 2010 09:55:13 +0300 Message-ID: <4C2C3BD1.2070207@held.org.il> References: <230ED15F81AFD3409345FFA4E565F0E50B83D8E1@NDHV3000.na.corp.mckesson.com> Reply-To: device-mapper development Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4642562786948755840==" Return-path: In-reply-to: <230ED15F81AFD3409345FFA4E565F0E50B83D8E1@NDHV3000.na.corp.mckesson.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dm-devel-bounces@redhat.com Errors-To: dm-devel-bounces@redhat.com To: dm-devel@redhat.com List-Id: dm-devel.ids This is a multi-part message in MIME format. --===============4642562786948755840== Content-type: multipart/alternative; boundary="Boundary_(ID_SBHBWzhYYm0SJ01PiiGpbA)" This is a multi-part message in MIME format. --Boundary_(ID_SBHBWzhYYm0SJ01PiiGpbA) Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT It's not an easy process. The rescan-scsi-bus.sh script was added in recent RHEL5 updates, already in old SLES. I guess it's becoming kind of a standard. On 07/01/10 04:00, Allen, Jack wrote: > > Hello: > What is the best way to cause the system to rescan for new LUNs, other > than rebooting? > > ----- > Jack Allen > > > -- > dm-devel mailing list > dm-devel@redhat.com > https://www.redhat.com/mailman/listinfo/dm-devel --Boundary_(ID_SBHBWzhYYm0SJ01PiiGpbA) Content-type: text/html; charset=ISO-8859-1 Content-transfer-encoding: 7BIT It's not an easy process.

The rescan-scsi-bus.sh script was added in recent RHEL5 updates, already in old SLES. I guess it's becoming kind of a standard.

On 07/01/10 04:00, Allen, Jack wrote:

Rescan for new LUNs
Hello:
What is the best way to cause the system to rescan for new LUNs, other than rebooting?

-----
Jack Allen
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel

--Boundary_(ID_SBHBWzhYYm0SJ01PiiGpbA)-- --===============4642562786948755840== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline --===============4642562786948755840==--