linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ric Wheeler <rwheeler@redhat.com>
To: linux-scsi@vger.kernel.org, kay.sievers@vrfy.org,
	Greg KH <greg@kroah.com>
Cc: Tom Coughlan <coughlan@redhat.com>
Subject: mpt2sas logged messages
Date: Tue, 18 Aug 2009 09:18:30 -0400	[thread overview]
Message-ID: <4A8AAA26.9090706@redhat.com> (raw)


We have a new toy to test very large & slow storage with built up from 5 
SAS expansion shelves (Promise Vtrak J-Class) with 60 S-ATA drives and 
16 SAS drives (the S-ATA drives each have a Promise Vtrak S-ATA MUX 
adapter daughter card in the disk sled).

The basic idea is to build a cheap & slow test bed for file & storage 
system scalability. Collectively, we have about 120TB (raw) of capacity 
to play with in one server.

As we work through various issues, a couple of oddities popped out.

The first is that udev grumbles during boot about "file name too long" 
like the following:

Aug 17 06:49:58 megadeth udevd-event[20447]: unable to create db file 
'/dev/.udev/db/\x2fdevices\x2fpci0000:00\x2f0000:00:04.0\x2f0000:17:00.0\x2f0000:18:0a.0\x2f0000:1f:00.0\x2fhost11\x2fport-11:0\x2fexpander-11:0\x2fport-11:0:0\x2fexpander-11:1\x2fport-11:1:0\x2fexpander-11:2\x2fport-11:2:17\x2fexpander-11:3\x2fport-11:3:1\x2fend_device-11:3:1\x2fbsg\x2fend_device-11:3:1': 
File name too long

The second is that the mpt2sas driver spews various messages like:

Aug 17 06:55:17 megadeth kernel: mpt2sas0: log_info(0x31120102): 
originator(PL), code(0x12), sub_code(0x0102)

Any insight into whether these are issues worth pursuing is appreciated, 
thanks!

Ric



             reply	other threads:[~2009-08-18 13:16 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-18 13:18 Ric Wheeler [this message]
2009-08-18 13:25 ` mpt2sas logged messages Greg KH
2009-08-18 13:55   ` James Bottomley
2009-08-18 13:59   ` Ric Wheeler
2009-08-18 14:57     ` Greg KH
2009-08-18 15:53       ` Ric Wheeler
2009-08-18 16:09         ` James Bottomley
2009-08-18 17:44           ` Ric Wheeler
2009-08-18 20:14             ` James Bottomley
2009-08-18 20:33               ` Ric Wheeler
2009-08-18 16:40         ` Greg KH
2009-08-18 17:45           ` Ric Wheeler
2009-08-18 18:37           ` Kay Sievers
2009-08-18 18:41             ` Ric Wheeler
2009-08-19 19:30               ` Kay Sievers
2009-08-19 19:36                 ` Ric Wheeler
2009-08-20 15:18                 ` Ric Wheeler
2009-08-20 15:20                   ` Kay Sievers
2009-08-20 15:30                     ` Ric Wheeler
2009-08-18 13:26 ` Ric Wheeler
2009-08-18 15:39 ` Moore, Eric
2009-08-18 16:13   ` James Bottomley
2009-08-18 17:02     ` Moore, Eric
2009-08-18 17:47       ` Ric Wheeler

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=4A8AAA26.9090706@redhat.com \
    --to=rwheeler@redhat.com \
    --cc=coughlan@redhat.com \
    --cc=greg@kroah.com \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-scsi@vger.kernel.org \
    /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).