From: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>
To: NeilBrown <neilb@suse.de>
Cc: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>,
linux-raid@vger.kernel.org
Subject: Re: Superblock backup
Date: Fri, 11 May 2012 20:15:34 +0200 [thread overview]
Message-ID: <20120511181534.GA2953@lazy.lzy> (raw)
In-Reply-To: <20120511085057.27790c1a@notabene.brown>
iHi Neil,
> > 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 :-)
actually, I was thinking "dd" because a restore
operation could be another "dd" (from file to device).
Does this make sense? Or old superblocks should
never replace newer ones?
I mean, let's say each day the first few MB of
each component device is stored somewhere.
As soon as some irreparable damage happens, the
files can be restored in the proper devices.
Practically rolling back to the previous day
the superblock status.
Would this work?
Thanks,
bye,
--
piergiorgio
prev parent reply other threads:[~2012-05-11 18:15 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
2012-05-11 18:15 ` Piergiorgio Sartor [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=20120511181534.GA2953@lazy.lzy \
--to=piergiorgio.sartor@nexgo.de \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.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).