linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: kustep <kustep@web.de>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: unused space before data offset mismatch
Date: Thu, 21 Nov 2013 14:33:30 +1100	[thread overview]
Message-ID: <20131121143330.326f8d45@notabene.brown> (raw)
In-Reply-To: <528D118D.7090800@web.de>

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

On Wed, 20 Nov 2013 20:46:21 +0100 kustep <kustep@web.de> wrote:

> Hello Everyone,
> 
> is there an option to specifiy the "Unused Space : before=...."
> Superblock information in mdadm -C ....?

 --data-offset=....

or 
  --data-offset=variable ... /dev/foo:16K  /dev/foo2:32K ....

You probably need mdadm 3.3.

NeilBrown

> 
> My Raid crashed due to a controller error, but I was able to make the
> new superblock almost identical to the old one (using mdadm -C
> --assume-clean --level=6 --raid-devices=11 --chunk=256K --metadata=1.2
> --bitmap=None --size=195328588 --data-offset=128768 /dev/md0
> /dev/mapper/disk[cdefmbjkh] missing). Looking at mdadm --examine the
> only difference left is:
> old layout: Unused Space : before=257456 sectors, after=197632 sectors
> new layout: Unused Space : before=257448 sectors, after=197632 sectors
> 
> Is there an option to change that or anything else I can do to make the
> layouts identical? The assembled raid refuses to mount, and I suspect
> this difference to be the reason.
> 
> Thanks in advance
> Stephan
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


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

      parent reply	other threads:[~2013-11-21  3:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-20 19:46 unused space before data offset mismatch kustep
2013-11-21  3:25 ` Phil Turmel
2013-11-21  3:33 ` NeilBrown [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=20131121143330.326f8d45@notabene.brown \
    --to=neilb@suse.de \
    --cc=kustep@web.de \
    --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;
as well as URLs for NNTP newsgroup(s).