From: NeilBrown <neilb@suse.de>
To: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: Superblock backup
Date: Fri, 11 May 2012 08:50:57 +1000 [thread overview]
Message-ID: <20120511085057.27790c1a@notabene.brown> (raw)
In-Reply-To: <20120510174431.GA3019@lazy.lzy>
[-- Attachment #1: Type: text/plain, Size: 1269 bytes --]
On Thu, 10 May 2012 19:44:31 +0200 Piergiorgio Sartor
<piergiorgio.sartor@nexgo.de> wrote:
> Hi,
>
> again, following the RAID-5 story, I was wondering
> if could make sense to have a new superblock type,
> let's say 2.x, having backup copies (of persistent
> or quasi persistent data) in different areas of the
> drive components.
> This would be similar to filesystem or gpt.
>
> Is there anything planned for this?
This is one of the idea that has floated around in my head for a while,
possibly a v1.3 metadata.
However my thought there was always to protect against a bad block on the
device. Protecting against data corruption due to bugs or sys-admin mistakes
is always best handled by backups.
e.g. take a 'dump' (either binary or textual) of the metadata every day, or
every reboot or something. (And store it on a different host).
Both are probably useful, but for the recently problem, a regular backup
would be the most useful.
>
> In any case, it would be still interesting to have
> a "backup" capability at hand, like a "dd" of the
> superblock to some secure file.
"mdadm -E" would probably be enough - just write a cron job :-)
NeilBrown
>
> Any idea or suggestions?
>
> Thanks,
>
> bye,
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-05-10 22:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-10 17:44 Superblock backup Piergiorgio Sartor
2012-05-10 22:50 ` NeilBrown [this message]
2012-05-11 18:15 ` Piergiorgio Sartor
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=20120511085057.27790c1a@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=piergiorgio.sartor@nexgo.de \
/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).