From: Caspar Smit <c.smit@truebit.nl>
To: Arne Jansen <lists@die-jansens.de>
Cc: linux-scsi@vger.kernel.org
Subject: Re: mpt2sas: bug in disk ordering?
Date: Fri, 13 May 2011 12:41:33 +0200 [thread overview]
Message-ID: <BANLkTi=QOSDOvgfXX9qqgdmOSicQpV4ViA@mail.gmail.com> (raw)
In-Reply-To: <4DCD09D9.4080702@die-jansens.de>
That is something I really don't like.
After more checking I noticed the /dev/disk/by-path doesn't have any
links for the disks and their slots anymore.
Kind regards,
Caspar Smit
Systemengineer
True Bit Resources B.V.
Ampèrestraat 13E
1446 TP Purmerend
T: +31(0)299 410 475
F: +31(0)299 410 476
@: c.smit@truebit.nl
W: www.truebit.nl
2011/5/13 Arne Jansen <lists@die-jansens.de>:
> On 13.05.2011 12:34, Caspar Smit wrote:
>> I tried with Debian Squeeze with the latest backports kernel 2.6.38,
>> which has mpt2sas version 07.100.00.00
>> and now the disks are ordered this way:
>>
>> /dev/sdb = slot 3
>> /dev/sdc = slot 2
>> /dev/sdd = slot 1
>> /dev/sde = slot 0
>> /dev/sdf = slot 7
>> /dev/sdg = slot 6
>> /dev/sdh = slot 5
>> /dev/sdi = slot 4
>
> I see something similar here, and, what's worse, the order may very from
> boot to boot.
>
> -Arne
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-05-13 10:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-13 9:19 mpt2sas: bug in disk ordering? Caspar Smit
2011-05-13 10:34 ` Caspar Smit
2011-05-13 10:37 ` Arne Jansen
2011-05-13 10:41 ` Caspar Smit [this message]
2011-05-13 10:51 ` Arne Jansen
2011-05-13 10:56 ` Caspar Smit
2011-05-13 11:15 ` Desai, Kashyap
2011-05-13 11:46 ` Caspar Smit
2011-05-13 12:03 ` Billy Crook
2011-05-13 12:05 ` Caspar Smit
2011-05-13 12:09 ` Mikael Abrahamsson
2011-05-13 14:39 ` James Bottomley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='BANLkTi=QOSDOvgfXX9qqgdmOSicQpV4ViA@mail.gmail.com' \
--to=c.smit@truebit.nl \
--cc=linux-scsi@vger.kernel.org \
--cc=lists@die-jansens.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).