All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Reed <mdr@sgi.com>
To: Hannes Reinecke <hare@suse.de>
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
	Jeremy Higdon <jeremy@sgi.com>, Tony Ernst <tee@sgi.com>
Subject: Re: [PATCH] sd name space exhaustion causes system hang
Date: Tue, 21 Sep 2010 10:58:42 -0500	[thread overview]
Message-ID: <4C98D632.8020000@sgi.com> (raw)
In-Reply-To: <4C98CA74.7060500@suse.de>



On 09/21/2010 10:08 AM, Hannes Reinecke wrote:
> Michael Reed wrote:
>> Following a site power outage which re-enabled all the ports on my FC
>> switches, my system subsequently booted with far too many luns!  I had
>> let it run hoping it would make multi-user.  It didn't.  :(  It hung solid
>> after exhausting the last sd device, sdzzz, and attempting to create sdaaaa
>> and beyond.  I was unable to get a dump.
>>
>> Discovered using a 2.6.32.13 based system.
>>
>> Patch at the bottom corrects this by detecting when the last index is
>> utilized and failing the sd probe of the device.  Patch applies to
>> scsi-misc-2.6.
>>
> Hmm. Shouldn't we rather use dynamic majors once we're over
> SD_MAJORS? We do have enough space in the 'index' field and the name
> is generated dynamically anyway ...

A bit beyond the scope of what I was trying to correct.  And beyond my
current knowledge of how things work.  If you'd care to guide me, or
provide me a patch for testing....  I can probably get my config up to
30,000 or so luns.

Mike

> 
> Cheers,
> 
> Hannes

  reply	other threads:[~2010-09-21 15:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-20 16:20 [PATCH] sd name space exhaustion causes system hang Michael Reed
2010-09-21 15:08 ` Hannes Reinecke
2010-09-21 15:58   ` Michael Reed [this message]
2010-09-21 17:16     ` Michael Reed

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=4C98D632.8020000@sgi.com \
    --to=mdr@sgi.com \
    --cc=hare@suse.de \
    --cc=jeremy@sgi.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=tee@sgi.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.