linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ninti Systems <office@ninti.com.au>
To: 'LinuxRaid' <linux-raid@vger.kernel.org>
Subject: RE: Please review: Slackware RAID How-To
Date: 20 May 2004 11:36:09 +0930	[thread overview]
Message-ID: <1085018769.2042.32.camel@localhost> (raw)
In-Reply-To: <1085017348.8670.26.camel@localhost>

But is the stride parameter required at all if I'm only building a RAID1
array with two disks?

Also, is the chunk size necessary in this case as I remember getting a
message on boot up to the effect that "Chunk size not necessary here,
but proceeding anyway!".

Thanks

Mick


On Thu, 2004-05-20 at 11:12, John Lange wrote:
> On Sun, 2004-05-16 at 23:51, Guy wrote:
> > md2 has 4 disks with a chunk size of 128K.  Since only 3 disks are used for
> > data, and the filesystem block size is 4K, the stride size should be
> > 128*3/4, or 96.
> > Change:
> > 	mke2fs -b 4096 -R stride=32 /dev/md2
> > To:
> > 	mke2fs -b 4096 -R stride=96 /dev/md2
> > 
> > My logic:
> > 	"Stripe size" is "chunk size" times "number of data disks".
> > 	From example:
> > 		"chunk size" = 128
> > 		"number of data disks" = "nr-raid-disks" - 1 (-2 if RAID6)
> 
> I think this is incorrect. At this point I defer to the
> Software-RAID-HOWTO.
> 
> http://www.tldp.org/HOWTO/Software-RAID-HOWTO-5.html#ss5.10
> 
> >From that document stride is chucksize/blocksize . Number of disks does
> not enter into it.
> 
> So with a chunksize of 128, and a block size of 4 it would be:
> 
> 128K/4K = 32 for stride.
> 
> If this is indeed correct I will be sure to expand that area of the
> How-To so it is more clear.
> 
> Thanks very much for your feedback.
> 
> Regards,
> 
> John Lange
> 
> -
> 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
-- 
--------------------------------------
Ninti Systems: Smart IT Solutions
Michael Hall
Mobile: 0429 095 392
Ph/Fax: 08 8953 1442       
Email:  office at ninti dot com dot au
Web:    http://ninti.com.au
--------------------------------------


  reply	other threads:[~2004-05-20  2:06 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-11 15:42 Please review: Slackware RAID How-To John Lange
2004-05-11 23:51 ` Ninti Systems
2004-05-16  5:43 ` Ninti Systems
2004-05-16  6:40 ` Ninti Systems
2004-05-17  2:36 ` Ninti Systems
2004-05-17  4:51   ` Guy
2004-05-17  9:02     ` Ninti Systems
2004-05-20  1:42     ` John Lange
2004-05-20  2:06       ` Ninti Systems [this message]
2004-05-20  3:27         ` Guy
2004-05-20  3:33         ` John Lange
2004-05-20  5:02           ` Guy
2004-05-20  7:58             ` John Lange
2004-05-20 13:37               ` Guy
2004-05-21  2:25               ` Ninti Systems
2004-05-21  2:55                 ` Guy
2004-05-21  2:47               ` Ninti Systems
2004-05-20  3:11       ` Guy
2004-05-20  4:35         ` Guy
  -- strict thread matches above, loose matches on Subject: below --
2004-05-13  9:46 George  Iosif
2004-05-14  6:21 George  Iosif
     [not found] <s0a48f9e.018@nsa.ase.ro>
2004-05-14  6:47 ` John Lange

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=1085018769.2042.32.camel@localhost \
    --to=office@ninti.com.au \
    --cc=linux-raid@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).