-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I've noticed that e2image doesn't get the backup superblocks and group
descriptors. Is this intentional or an oversight? Is there a way to
resync the backups from the master copy? e2fsck doesn't seem to do it.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJPQmg/AAoJEJrBOlT6nu75XqsH/2sZKmffNTRSGIdM3DWi01Kf
aSrDy9rGcyiXd1L8ZhqdXkajCaLuweXBgUfM45mCvdXfd2T5ZgTkg5djc5xuOdPi
qyz4DmJwksMVtrGGliwnFXG6wypiHDdpO3ntVcudCOSkXPO+ESYFKlQV4cX3Dx70
0r+n2hjNHBIuwcBsIdOVzOc4tL0mDqVub/owHSAgI84KDEnCxsIievKS0PYMQpEr
zY64x6KB2Oh8Q8UXZyMZ7ddJpbYFSm/Dpr5eFwFpqRsSTMSV4Z5vYcvVYmuxWBbX
XSbT2D9LsAbuHCGld7X4vSmfFRYij6xR/+5DXIK9kawFvKcxmjNWywu0ZlbuvCY=
=t5up
-----END PGP SIGNATURE-----
On Mon, Feb 20, 2012 at 10:35:27AM -0500, Phillip Susi wrote:
>
> I've noticed that e2image doesn't get the backup superblocks and group
> descriptors. Is this intentional or an oversight?
It's deliberate. I suppose it might be useful if you are using
e2image -r to make a copy of a corrupted file system, where the
primary superblocks are corrupted. It's probably reasonable to save a
copy of the first backup superblock just so that e2fsck run on the raw
image mimicks what you'd see if you were running on the same file
system. I'd accept a patch to do this.
> Is there a way to resync the backups from the master copy? e2fsck
> doesn't seem to do it.
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.
But if you really do want to copy the master superblock and block
descriptor blocks ot backups, you can do it via the following:
debugfs -w /dev/sdb1
debugfs: dirty
debugfs: close -a
debugfs: quit
Regards,
- Ted
-----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-----