Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Wols Lists <antlists@youngman.org.uk>
To: Duane <duane@evenson.tk>, linux-raid <linux-raid@vger.kernel.org>
Subject: Re: very large data-offset?
Date: Thu, 30 Nov 2017 10:45:09 +0000	[thread overview]
Message-ID: <5A1FE135.8090000@youngman.org.uk> (raw)
In-Reply-To: <f5ff4798-5717-8b00-a293-463f202259b1@evenson.tk>

On 30/11/17 10:26, 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.
> 
> 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.
> 
> When reshaping the array, I am prompted to use an external file, so I
> don't see that mdadm ever uses the space.
> 
Do you mean the manual tells you, or that mdadm refuses to run otherwise?

Certainly with a new array on larger disks, a backup file should be
totally unnecessary.

Run a reshape of some sort, and see if the offset changes :-)
> 
> 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?
> 
Dunno. How do you know the bitmap is "just one block"? I haven't dug in
to it so I don't know, but it makes sense to me that as the disks get
bigger, so does the bitmap.

What's the point of fighting the defaults, anyway? Just add
another/bigger disk if you need more space.

Cheers,
Wol


  reply	other threads:[~2017-11-30 10:45 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 [this message]
2017-12-05  3:26   ` Duane
2017-12-04  0:51 ` NeilBrown
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=5A1FE135.8090000@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --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