linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Specifying a data offset?
@ 2013-05-08 20:17 Tregaron Bayly
  2013-05-08 20:44 ` Phil Turmel
  0 siblings, 1 reply; 3+ messages in thread
From: Tregaron Bayly @ 2013-05-08 20:17 UTC (permalink / raw)
  To: linux-raid

We have lots of mirrors all over our network and over time this means
arrays created by different versions of mdadm.  In turn this means that
we have all sorts of data offsets, including a 2.3.5 mdadm version that
offset the data 262,144 sectors.  I can't fathom why I need my data to
start 128M from the beginning of the disk, but whatever.

Inevitably an admin decided that doing a --create over the top of an
existing array was a good and necessary thing and when finished we
couldn't find the filesystem.  Bringing it back online was simply a case
of finding the correct offset, locating an mdadm version that would
specify it properly and doing another create.  Through the whole
exercise I found myself wondering why there isn't a command line
argument to specify the data offset if something other than the default
is desired.  I think that implementing the argument and reading the
value in init_super wouldn't be terribly difficult so I must be missing
an obvious reason.  Can someone explain to me why this feature isn't
desirable?

Thanks,

Tregaron


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Specifying a data offset?
  2013-05-08 20:17 Specifying a data offset? Tregaron Bayly
@ 2013-05-08 20:44 ` Phil Turmel
  2013-05-08 23:03   ` Tregaron Bayly
  0 siblings, 1 reply; 3+ messages in thread
From: Phil Turmel @ 2013-05-08 20:44 UTC (permalink / raw)
  To: tbayly; +Cc: linux-raid

On 05/08/2013 04:17 PM, Tregaron Bayly wrote:
> We have lots of mirrors all over our network and over time this means
> arrays created by different versions of mdadm.  In turn this means that
> we have all sorts of data offsets, including a 2.3.5 mdadm version that
> offset the data 262,144 sectors.  I can't fathom why I need my data to
> start 128M from the beginning of the disk, but whatever.
> 
> Inevitably an admin decided that doing a --create over the top of an
> existing array was a good and necessary thing and when finished we
> couldn't find the filesystem.  Bringing it back online was simply a case
> of finding the correct offset, locating an mdadm version that would
> specify it properly and doing another create.  Through the whole
> exercise I found myself wondering why there isn't a command line
> argument to specify the data offset if something other than the default
> is desired.  I think that implementing the argument and reading the
> value in init_super wouldn't be terribly difficult so I must be missing
> an obvious reason.  Can someone explain to me why this feature isn't
> desirable?

This desirable and has been implemented.  Check out the development
version of mdadm and look at the "--data-offset" option.

It does not exist in a released version yet, but it has been cooking
since October.

Phil

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Specifying a data offset?
  2013-05-08 20:44 ` Phil Turmel
@ 2013-05-08 23:03   ` Tregaron Bayly
  0 siblings, 0 replies; 3+ messages in thread
From: Tregaron Bayly @ 2013-05-08 23:03 UTC (permalink / raw)
  To: Phil Turmel; +Cc: linux-raid

On Wed, 2013-05-08 at 16:44 -0400, Phil Turmel wrote:

> This desirable and has been implemented.  Check out the development
> version of mdadm and look at the "--data-offset" option.
> 
> It does not exist in a released version yet, but it has been cooking
> since October.

Ah, very nice.  Thanks!




^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2013-05-08 23:03 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-05-08 20:17 Specifying a data offset? Tregaron Bayly
2013-05-08 20:44 ` Phil Turmel
2013-05-08 23:03   ` Tregaron Bayly

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).