Bug 22657 - uninitialized data left in journal error field after e2fsck
Summary: uninitialized data left in journal error field after e2fsck
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat High Availability Server
Classification: Retired
Component: ext3
Version: 1.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Stephen Tweedie
QA Contact: Wil Harris
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-12-21 11:26 UTC by Gerald Britton
Modified: 2007-04-18 16:30 UTC (History)
0 users

(edit)
Clone Of:
(edit)
Last Closed: 2000-12-21 23:45:32 UTC


Attachments (Terms of Use)

Description Gerald Britton 2000-12-21 11:26:33 UTC
When running e2fsck on a v1 filesystem, the error field is left in an
uninitialized state
which will then be falsely interpreted as an error in the filesystem.

Comment 1 Stephen Tweedie 2000-12-21 23:45:29 UTC
I can't reproduce this using the current e2fsprogs on
ftp.uk.linux.org:/pub/linux/sct/fs/jfs/e2fsprogs/.  Could you see if that helps?
 If not, a little more detail on the versions you are using here would help.

Comment 2 Stephen Tweedie 2001-01-12 13:43:41 UTC
I found a place where kernel journal initialisation was not correctly
initialising all journal fields.  Should be fixed in ext3-0.0.5e.


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