Suse sles10 SP1 -> SP2 update question

Suse sles10 SP1 -> SP2 update question

[Charlie Sharkey]

[-- Attachment #1.1: Type: text/plain, Size: 898 bytes --]

 
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.
 
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:
 
    util-linux, util-linux-crypto, scsi, multipath-tools, device-mapper,
udev, lvm2
 
Are there other dependencies that the device mapper needs for mounting ?
 
Thank you,
 
charlie

[-- Attachment #1.2: Type: text/html, Size: 3208 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]

Re: Suse sles10 SP1 -> SP2 update question

[Bryn M. Reeves]

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.