linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Klauer <Andreas.Klauer@metamorpher.de>
To: Peter Hoffmann <Hoffmann.P@gmx.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: Panicked and deleted superblock
Date: Tue, 1 Nov 2016 00:03:55 +0100	[thread overview]
Message-ID: <20161031230355.GA1825@metamorpher.de> (raw)
In-Reply-To: <9d0bf300-73e8-9109-c630-03f392fc820e@gmx.net>

On Mon, Oct 31, 2016 at 11:36:39PM +0100, Peter Hoffmann wrote:
> I'm a bit confused using the overlay function.

There really needs to be a standard utility for this.

Well, the "overlay manipulation functions" on that wiki page come close. 
You can paste/source those once in the shell and use them like commands. 
You need two sets of overlays, so you'd also have to create two sets of 
those functions (using different mapper names).

You should verify that the overlay itself is good by comparing the size 
(blockdev --getsize64 /dev/thing /dev/mapper/overlaything) as well as 
the content (cmp /dev/thing /dev/mapper/thething, no output if there is 
no difference, you can ctrl-c).

>     mdadm --create --assume-clean --level=5 --raid-devices=4 /dev/md0

This is wrong, or rather, when re-creating RAID you must be much more 
verbose with the options. http://unix.stackexchange.com/a/131927/30851

> Both ways should look exactly the same at least for the first 1200M,
> shouldn't they?

If you deliberately created smaller overlays, mdadm uses different 
defaults depending on device size too. If you expect it to be identical 
also check that --examine (data offset etc.) looks identical.

There's no point in using overlays that are not identical to the 
devices they're overlaying.

Regards
Andreas Klauer

  reply	other threads:[~2016-10-31 23:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-30 18:23 Panicked and deleted superblock Peter Hoffmann
2016-10-30 19:43 ` Andreas Klauer
2016-10-30 20:45   ` Peter Hoffmann
2016-10-30 21:11     ` Andreas Klauer
2016-10-31 22:36       ` Peter Hoffmann
2016-10-31 23:03         ` Andreas Klauer [this message]
2016-11-04  4:34 ` 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=20161031230355.GA1825@metamorpher.de \
    --to=andreas.klauer@metamorpher.de \
    --cc=Hoffmann.P@gmx.net \
    --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).