linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tyler <pml@dtbb.net>
To: "Peter T. Breuer" <ptb@lab.it.uc3m.es>
Cc: linux-raid@vger.kernel.org
Subject: Re: Any way to Increase MD_SB_DISKS=27 ? I need 31 devices
Date: Mon, 02 May 2005 01:40:34 -0700	[thread overview]
Message-ID: <4275E782.6090509@dtbb.net> (raw)
In-Reply-To: <4b0hk2-1gn.ln1@news.it.uc3m.es>

Peter, after looking at the code after i sent the email, I more or less 
figured out what you put below, i'm wondering though, will changing the 
structures here affect anything else? other than the mdadm tool.. what 
about mkfs.ext3/xfs and possibly mount?

Thanks,
Tyler.

Peter T. Breuer wrote:

>Tyler <pml@dtbb.net> wrote:
>  
>
>>I'd like to build a Raid-6 array using 31 drives, is there a patch 
>>available or an easy way to safely increase the *MD_SB_DISKS*=27 to a 
>>higher number?  My attempts at patching the source myself were 
>>unsuccessful, more than likely because i don't know what/why the limit 
>>is 27, and whether that effects other parts of the kernel.
>>    
>>
>
>It's 27 because that's how much space there is in some of the structs.
>
>Look in include/linux/raid. md_p.h, for example.
>
>   #define MD_SB_DISKS                     27
>
>and it calculates how much space that needs:
>
>   #define MD_SB_DISKS_WORDS (MD_SB_DISKS*MD_SB_DESCRIPTOR_WORDS)
>   #define MD_SB_DESCRIPTOR_WORDS          32
>
>and all that is part of what must fit in a "mdp_superblock_s" struct.
>
>           /*
>            * Disks information
>            */
>           mdp_disk_t disks[MD_SB_DISKS];
>
>with the space at the tail of the struct calculated ...
>
>
>        /*
>         * Reserved
>         */
>        __u32 reserved[MD_SB_RESERVED_WORDS];
>
> ... by figuring how much space was used and subtracting from 1K:
>
>       #define MD_SB_RESERVED_WORDS            (1024 - MD_SB_GENERIC_WORDS - MD_SB_PERSONALITY_WORDS - MD_SB_DISKS_WORDS - MD_SB_DESCRIPTOR_WORDS)
>
>and the space used includes the MD_SB_DESCRIPTOR_WORDS conisting of
>those 27 32-byte array elements.
>
>To make this number bigger, you would first have to make more room in
>the struct, by changing the 1K in the calculation to 4096 (thus
>extending the struct by extending its reserved section), then you
>could use more of that room by increasing the 27. I presume the max
>would now be 3*32+27 = 123.
>
>
>There might be another such struct in the includes. I haven't looked
> ...
>
>Peter
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-raid" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>
>  
>


  reply	other threads:[~2005-05-02  8:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-02  1:35 Any way to Increase MD_SB_DISKS=27 ? I need 31 devices Tyler
2005-05-02  7:09 ` Peter T. Breuer
2005-05-02  8:40   ` Tyler [this message]
2005-05-02  8:56     ` Peter T. Breuer
2005-05-02  9:36       ` Peter T. Breuer
2005-05-03 11:44         ` Tyler
2005-05-03 13:45           ` Peter T. Breuer
2005-05-02 14:58 ` Paul Clements
2005-05-03 11:22   ` Tyler
2005-05-03 14:03     ` Paul Clements
2005-05-03 22:28       ` Tyler

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=4275E782.6090509@dtbb.net \
    --to=pml@dtbb.net \
    --cc=linux-raid@vger.kernel.org \
    --cc=ptb@lab.it.uc3m.es \
    /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).