From: Rasmus Plewe (rplewe_at_suse.de)
Date: Fri Jul 20 2007 - 13:18:34 CEST
Date: Fri, 20 Jul 2007 13:18:34 +0200 From: Rasmus Plewe <rplewe@suse.de> Message-ID: <20070720111834.GD1697@coredump.suse.de> Subject: Re: [suse-sles-e] SLES 10 SP1 changes of fusion (LSI) driver
Hello,
On Mon, Jul 16, 2007 at 01:56:55PM +0200, matilda matilda wrote:
>
> thank you for your answer.
> Probably my question was not precise enough.
>
> 1) I do have only one physical connection to the DS3200. So, I do have
> only ONE path to a defined lun. BUT: With SLES 10 (w/o SP1) I saw
> 4 scsi devices when I ran 'lsscsi'. E.g.:
> =======================================================================
> [3:4:0:1] disk IBM 1726-2xx FAStT 0617 -
> [3:4:0:2] disk IBM 1726-2xx FAStT 0617 -
> [3:4:0:3] disk IBM 1726-2xx FAStT 0617 -
> [3:4:0:31] disk IBM Universal Xport 0617 -
> =======================================================================
>
> Yes, when I installed SLES 10 I was wondering about that picture.
> As you see there is NO device node for a detected block device.
> As soon as I installed RDAC driver ontop of that, I got an additional
> entry like:
> =======================================================================
> [5:0:0:1] disk IBM VirtualDisk 0617 /dev/sdb
> =======================================================================
> On this device I could operate.
>
> Now, after installing SP1, I see a totally different picture:
> I see exactly only the block device I can operate on and a controlling
> scsi device as before, e.g:
> =======================================================================
> [3:0:0:3] disk IBM 1726-2xx FAStT 0617 /dev/sdd
> [3:0:0:31] disk IBM Universal Xport 0617 -
> =======================================================================
>
> So, probably we do have a situation NOW which is as I expected it.
> But something relevant changed. And I want to know what parts of the
> fusion drivers changed, so that I do see a totally different situation
> after upgrading. I want to get sure, that everything is fine with the
> storage subsystem.
the response I got was a laconic "yes, I know, boot loader configuration
is working correctly now". So the changes weren't in the driver but in
the way the system is set up. The lines in /boot/grub/menu.lst should be
the only thing that has really changed.
Regards,
Rasmus
-- Rasmus Plewe --- Linux Beta Test Coordinator SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) Maxfeldstrasse 5, D-90409 Nuernberg --------------------------------------------------------------------- To unsubscribe, e-mail: suse-sles-e-unsubscribe@suse.com For additional commands, e-mail: suse-sles-e-help@suse.com
This archive was generated by hypermail 2.1.7 : Fri Jul 20 2007 - 15:22:15 CEST