From: Phillip Susi <psusi@ubuntu.com>
To: Ted Ts'o <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org
Subject: Re: e2image doesn't get backup superblocks?
Date: Mon, 20 Feb 2012 14:22:34 -0500 [thread overview]
Message-ID: <4F429D7A.7080202@ubuntu.com> (raw)
In-Reply-To: <20120220190535.GA6541@thunk.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 2/20/2012 2:05 PM, Ted Ts'o wrote:
> Why do you want to do this? In general the tools will
> automatically sync the backups from the master if it is necessary
> (i.e., in the case of a file system resize, or if there is a
> change in the file system features). Otherwise, we deliberately
> try to avoid modifying the backups, since any updates to the
> backups is an opportunity to copy corrupted values to the backups,
> or otherwise risk write failures that could smash the backups.
Because I was experimenting with e2fsck -E discard on a raw image and
it was clobbering the superblock, and the backups weren't in the
image.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJPQp16AAoJEJrBOlT6nu75YsYH/RfMeeqyq1YzolyRJzeQuQVB
vi1sKkW8LlYutAU3bgJPPxNa3VEUlz5BDqOLzL2DZcsUWUU0t/XkwWGBW8M5UPuy
LQyc/DO2Uz+ho8Jh+WSaOT0FByE5Gp4o5Xu5nhdO27MuTa1q0WiAxGneTnoN+ZNW
G2FkaTAWEGTPhUzV8F32ZnfKNzGJExl5BhiBEm5p5d2jqdzrQS4Uz15ZDbIqSmnL
uJNmtdcBjvq721Rcrf9U15TzZgumxy4VVaNNqR1ZhFG+HnGUVmsqC6HQ1/WaQHWh
WqyXdgX1SlCPP2oAYE8pRvhLQkujg553QBYKkuckQfXD8YnpFWWFQ3fsGLWG5+c=
=cqFo
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2012-02-20 19:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-20 15:35 e2image doesn't get backup superblocks? Phillip Susi
2012-02-20 19:05 ` Ted Ts'o
2012-02-20 19:22 ` Phillip Susi [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=4F429D7A.7080202@ubuntu.com \
--to=psusi@ubuntu.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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