All of lore.kernel.org
 help / color / mirror / Atom feed
From: guy keren <choo@actcom.co.il>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: max number of paths
Date: Mon, 15 Mar 2010 22:46:11 +0200	[thread overview]
Message-ID: <4B9E9C93.2050202@actcom.co.il> (raw)
In-Reply-To: <03FB5D708BE3C8448E8079186A56CDE60162B9F9@BTIBURMAIL.bustech.com>


do the devices look something like /dev/sd*, or /dev/cciss/* or 
something similar? if the later - it _could_ be a driver-specific issue, 
and i would look for info about the specific block driver.

--guy

Charlie Sharkey wrote:
> I'm seeing this on a Suse Sles10 x86_64 system, 2.6.16.60-0.34-smp.
> I have a qlogic qle2462 connected to a hp eva back end. 
> 
> 
> 
> -----Original Message-----
> From: dm-devel-bounces@redhat.com [mailto:dm-devel-bounces@redhat.com]
> On Behalf Of guy keren
> Sent: Monday, March 15, 2010 4:15 PM
> To: device-mapper development
> Subject: Re: [dm-devel] max number of paths
> 
> 
> Charlie Sharkey wrote:
>>  
>>
>> Is there a maximum number of paths supported by the device mapper ?
>>
>> I have a setup with 12 paths to 14 luns. I had to reduce the number of
> paths
>> to 10 for the device mapper to startup correctly.
> 
> i have seen such problems with linux kernel 2.4, long ago, when max SCSI
> 
> disk devices was 256 (and hence - also max paths for such devices).
> 
> if you're not using SCSI, but rather some other type of device - it 
> could be a limitation of the specific low level driver.
> 
> which kernel are you using? and which linux distribution? and what kind 
> of block devices do your disks reside on?
> 
> --guy
> 
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
> 
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel

      reply	other threads:[~2010-03-15 20:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-15 18:30 max number of paths Charlie Sharkey
2010-03-15 20:15 ` guy keren
2010-03-15 20:26   ` Charlie Sharkey
2010-03-15 20:46     ` guy keren [this message]

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=4B9E9C93.2050202@actcom.co.il \
    --to=choo@actcom.co.il \
    --cc=dm-devel@redhat.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.