All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: linux-raid@vger.kernel.org
Subject: Re: [patch] linear does not need chunksize
Date: Sun, 17 Jul 2005 03:50:48 +0400	[thread overview]
Message-ID: <42D99D58.6080207@tls.msk.ru> (raw)
In-Reply-To: <17113.38562.489541.760889@cse.unsw.edu.au>

Neil Brown wrote:
> On Sunday July 17, mjt@tls.msk.ru wrote:
[]
>>Note chunk size is never used on linear array.  The
>>only usage of chunk_size member is in /proc/mdstat,
>>as "rounding" parameter (linear.c) - looks like it
>>should be removed too.
> 
> This statement isn't entirely true, though it took me a little while
> to remind myself exactly how linear.c does use chunk_size.
> 
> linear_run in linear.c uses rdev->size for each devices.
> in md.c rdev->size is set by a call to calc_dev_size()
> calc_dev_size *does* use chunk_size (if it is non-zero)

Aha.

Well, in that case, the whole stuff around that check should
be reviewed.  At least, all the various raid levels should
have device size to be at least PAGE_SIZE (as checked in the
code fragment surrounded by this if() statement).

BTW, I don't really know how we got zero chunksize in the
superblock in the first place.  It was evms who screwed up
3-components linear array somehow (which worked before),
and, since I for one know nothing about evms, we tried to
assemble it with mdadm, which failed due to this very check
in kernel.  So we were forced to re-create the array to
work around this in-kernel check (since for linear array
recreate operation is safe and leaves the data intact).

So maybe the whole issue is moot: how often do you see
an array with zero chunk-size?

Thanks.

/mjt

      reply	other threads:[~2005-07-16 23:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-16 23:12 [patch] linear does not need chunksize Michael Tokarev
2005-07-16 23:22 ` Neil Brown
2005-07-16 23:50   ` Michael Tokarev [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=42D99D58.6080207@tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@cse.unsw.edu.au \
    /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.