From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Charlie Sharkey" Subject: Suse sles10 SP1 -> SP2 update question Date: Tue, 6 Jan 2009 15:56:59 -0500 Message-ID: <03FB5D708BE3C8448E8079186A56CDE60104231E@BTIBURMAIL.bustech.com> Reply-To: device-mapper development Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1351431950==" Return-path: Content-class: urn:content-classes:message 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. --===============1351431950== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C97041.51A2BAAE" This is a multi-part message in MIME format. ------_=_NextPart_001_01C97041.51A2BAAE Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable =20 I'm not sure if this is the correct place for this question or not. If not, please let me know. =20 After updating my Suse Sles10 SP1 system (2.6.16.46-0.12-smp) with the kernel rpm from SP2 (2.6.16.60-0.21-smp) devices that mounted (by label) are mounting as non multipathed devices. For example, a device that previously mounted as: /dev/dm-5 now mounts as: /dev/sdj1 =20 =20 The devices mount ok, they're just not mounting as multipathed devices.=20 If I reboot, there is about a one in five chance that they will mount ok. =20 I have tried updating the rpms that I thought might be needed by the new kernel, but haven't been able to correct the problem. I've updated the following rpms: =20 util-linux, util-linux-crypto, scsi, multipath-tools, device-mapper, udev, lvm2 =20 Are there other dependencies that the device mapper needs for mounting ? =20 Thank you, =20 charlie ------_=_NextPart_001_01C97041.51A2BAAE Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I'm = not sure if this=20 is the correct place for this question or not.

If = not, please let=20 me know.

After = updating my=20 Suse Sles10 SP1 system (2.6.16.46-0.12-smp) with=20 the

kernel = rpm from SP2=20 (2.6.16.60-0.21-smp) devices that mounted (by label)

are = mounting as=20 non multipathed devices. For example, a device that=20 previously

mounted as:=20 /dev/dm-5 now mounts as: /dev/sdj1 =

The=20 devices mount ok, they're just not mounting as multipathed devices. =

If I = reboot, there=20 is about a one in five chance that they will mount ok.

I have = tried=20 updating the rpms that I thought might be needed by the new kernel,=20 but

haven't been able to=20 correct the problem. I've updated the following = rpms:

=20 util-linux, util-linux-crypto, scsi, multipath-tools, device-mapper, = udev,=20 lvm2

Are = there other=20 dependencies that the device mapper needs for mounting = ?

Thank=20 you,

charlie

------_=_NextPart_001_01C97041.51A2BAAE-- --===============1351431950== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline --===============1351431950==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Bryn M. Reeves" Subject: Re: Suse sles10 SP1 -> SP2 update question Date: Wed, 07 Jan 2009 10:42:15 +0000 Message-ID: <49648707.6000903@redhat.com> References: <03FB5D708BE3C8448E8079186A56CDE60104231E@BTIBURMAIL.bustech.com> Reply-To: bmr@redhat.com, device-mapper development Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <03FB5D708BE3C8448E8079186A56CDE60104231E@BTIBURMAIL.bustech.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: device-mapper development List-Id: dm-devel.ids Charlie Sharkey wrote: > > I'm not sure if this is the correct place for this question or not. > If not, please let me know. > > After updating my Suse Sles10 SP1 system (2.6.16.46-0.12-smp) with the > kernel rpm from SP2 (2.6.16.60-0.21-smp) devices that mounted (by label) > are mounting as non multipathed devices. For example, a device that > previously > mounted as: /dev/dm-5 now mounts as: /dev/sdj1 > > The devices mount ok, they're just not mounting as multipathed devices. > If I reboot, there is about a one in five chance that they will mount > ok. The fact that there's a one in five or so chance it'll work suggests a race somewhere. I've often seen these with new kernels that take a bit longer to initialise the underlying SCSI devices, causing them to be absent when the initscripts run the multipath command to detect and configure multipath maps. I'm not sure exactly where this is done in the SuSE initscripts, but it should be easy enough to find with a bit of grepping. Try adding a "sleep 5" just before the multipath command runs. Alternately, if SLES10 supports the udevsettle command that gives a more elegant way of syncing up with udev's device creation. Instead of a sleep add a command like: udevsettle --timeout=30 We've added these to some of the RHEL5 initscripts to fix bugs like this. Regards, Bryn.