Linux RAID subsystem development
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.com>
To: Duane <duane@evenson.tk>, linux-raid <linux-raid@vger.kernel.org>
Subject: Re: very large data-offset?
Date: Mon, 04 Dec 2017 11:51:41 +1100	[thread overview]
Message-ID: <87po7vtiw2.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <f5ff4798-5717-8b00-a293-463f202259b1@evenson.tk>

[-- Attachment #1: Type: text/plain, Size: 1098 bytes --]

On Thu, Nov 30 2017, Duane wrote:

> Why is the data offset set so big? I created a 3x4TB RAID5 array and the 
> data offset was 128MB. Chunk size was the default 512kB.

It is less than 0.1% of the device...

>
> I cannot see why such a large offset is used. I would think the data 
> offset need only be at most the chunk size plus the space (1 sector) for 
> the superblock and bitmap.

It is insurance.  If you want to change the chunksize later, having a
lot of head-room will allow the reshape to go much faster.

>
> When reshaping the array, I am prompted to use an external file, so I 
> don't see that mdadm ever uses the space.

Citation needed.... what version of mdadm, what kernel?  What reshape
command?

>
>
> I tried making some test arrays and got much smaller sizes. A 3x1GB 
> RAID5 array with 64k chunks had a 1MB data offset.
>
>
> If I make a 7x4TB RAID5 array with 64kB chunks, is there a problem with 
> setting the data offset to around 2MB?

Only that it might reduce your options in the future, though probably
not by much.

NeilBrown

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  parent reply	other threads:[~2017-12-04  0:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-30 10:26 very large data-offset? Duane
2017-11-30 10:45 ` Wols Lists
2017-12-05  3:26   ` Duane
2017-12-04  0:51 ` NeilBrown [this message]
2017-12-05  3:33   ` Duane
2017-12-05 21:53     ` NeilBrown

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=87po7vtiw2.fsf@notabene.neil.brown.name \
    --to=neilb@suse.com \
    --cc=duane@evenson.tk \
    --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