Bug 21753 - Removing journal causes e2fsck full check.
Removing journal causes e2fsck full check.
Status: CLOSED CURRENTRELEASE
Product: Red Hat High Availability Server
Classification: Retired
Component: ext3 (Show other bugs)
beta
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Stephen Tweedie
Wil Harris
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2000-12-05 13:13 EST by Nalin Dahyabhai
Modified: 2007-04-18 12:30 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-12-22 11:33:51 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Force full fsck if we remove a reserved journal inode. (1.53 KB, patch)
2000-12-22 11:33 EST, Stephen Tweedie
no flags Details | Diff

  None (edit)
Description Nalin Dahyabhai 2000-12-05 13:13:03 EST
When you remove the has_journal flag with debugfs and reboot, fsck notes
that you have a journal but no has_journal flag set.  It then removes the
journal file, but leaves the inode intact.
The next time you run fsck, it notices that the inode is still there, and
forces a full check, which corrects this error.
I've seen this once, and didn't think enough to try to reproduce it after
that.  Let me know if you need me to.
Comment 1 Stephen Tweedie 2000-12-22 11:05:39 EST
Reproduced, and this looks easy to fix.  More shortly.
Comment 2 Stephen Tweedie 2000-12-22 11:33:49 EST
Created attachment 6678 [details]
Force full fsck if we remove a reserved journal inode.
Comment 3 Stephen Tweedie 2000-12-22 11:35:14 EST
Should be fixed in the attached patch.  I am currently building RPMs and this
will be included in my e2fsprogs-1.20.WIP.sct.20001222 interim release while I
sync up with Ted again.

Note You need to log in before you can comment on or make changes to this bug.