Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Ari Pollak <ari@debian.org>
To: linux-raid@vger.kernel.org
Subject: Re: Invalid argument when creating a RAID-0 array
Date: Sat, 14 Jun 2003 19:04:18 -0400	[thread overview]
Message-ID: <3EEBA9F2.7060902@debian.org> (raw)
In-Reply-To: <16107.43382.98190.258955@gargle.gargle.HOWL>

>>[Please CC me on replies]

>>too small chunk_size: 4096 < 8192
> 
> 
> Maybe use a bigger chunk size, 4K is rather small.
> However I thought 4k would work.  Maybe you aren't using an i386, as
> the minimum chunksize is currently connected with the system
> pagesize.  What architecture are you using?

Oops, I forgot to specify. I'm using an UltraSPARC on a Sun Enterprise 
450, using kernel 2.4.19 (I haven't had a chance to try .21 yet). I was 
just following the Software-RAID HOWTO, which said that for striping, 
chunksize didn't really matter.


  reply	other threads:[~2003-06-14 23:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-14 14:53 Invalid argument when creating a RAID-0 array Ari Pollak
2003-06-14 23:02 ` Neil Brown
2003-06-14 23:04   ` Ari Pollak [this message]
2003-06-15  8:14     ` Riley Williams

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=3EEBA9F2.7060902@debian.org \
    --to=ari@debian.org \
    --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