Bug 1097061
| Summary: | e2image can be run on a mounted filesystem | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Lachlan McIlroy <lmcilroy> |
| Component: | e2fsprogs | Assignee: | Eric Sandeen <esandeen> |
| Status: | CLOSED ERRATA | QA Contact: | dhe |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.4 | CC: | eguan, sct, vgaikwad |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | e2fsprogs-1.41.12-20.el6 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-10-14 07:54:19 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Lachlan McIlroy
2014-05-13 05:55:42 UTC
Here's an example from case 01089633: After restoring the image I ran 'e2fsck -fn /dev/loop0' and there were only a couple of errors: e2fsck 1.41.14 (22-Dec-2010) Warning: skipping journal recovery because doing a read-only filesystem check. Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information Free blocks count wrong (504542647, counted=497830816). Fix? no Free inodes count wrong (128163829, counted=128152494). Fix? no /dev/loop0: ********** WARNING: Filesystem still has errors ********** /dev/loop0: 11/128163840 files (1863.6% non-contiguous), 8094804/512637451 blocks Running e2fsck -fy /dev/loop0 reported a whole lot of errors starting with: e2fsck 1.41.14 (22-Dec-2010) /dev/loop0: recovering journal e2fsck: Group descriptors look bad... trying backup blocks... e2fsck: Bad magic number in super-block when using the backup blocks e2fsck: going back to original superblock Note: if several inode or block bitmap blocks or part of the inode table require relocation, you may wish to try running e2fsck with the '-b 32768' option first. The problem may lie only with the primary block group descriptors, and the backup block group descriptors may be OK. Block bitmap for group 13824 is not in group. (block 2553887680) Relocate? yes One or more block group descriptor checksums are invalid. Fix? yes ... It would seem that recovering the journal has done more damage to the filesystem than was already present. Agreed. I asked Carlos to fix this and he sent a patch upstream: [PATCH] e2image: Print a warning if running over a mounted filesystem Several users use to run e2image over a mounted RW filesystem, providing inconsistent, useless e2images for debugging purposes. This patch adds a warning in such cases, notifying the user and also adds a force option making e2image able to run in such cases. Also print a warning when not using qcow or raw formats but allows image creation to proceed, since, such images might be used for metadata backup purposes. Signed-off-by: Carlos Maiolino <cmaiolino> --- I think it's committed; if not I'll hassle Ted - may as well fix this now. Thanks Eric. Here to serve, Lachlan. ;) Moving back to ASSIGNED to try to get blocker status so I can fix the defect coverity found after I filed the errata... Never mind, not going to fix it this late in release. Eguan, can you set it back to verified? I'll file a new bug to track the coverity issue for 6.7 Bug 1139936 for the coverity defect issue. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-1566.html |