Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 7529 - file system corruption
file system corruption
Status: CLOSED DUPLICATE of bug 7506
Product: Red Hat Linux
Classification: Retired
Component: filesystem (Show other bugs)
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Bill Nottingham
Depends On:
  Show dependency treegraph
Reported: 1999-12-03 00:07 EST by rehbein
Modified: 2014-03-16 22:11 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 1999-12-06 12:12:52 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description rehbein 1999-12-03 00:07:03 EST
This is additional information to the bug being reported (previous bug
report 7506).
After reformatting the 36 gigabyte drive, a redownloaded some software, and
began performing a number of installations on the drive (approx 2 gig).
No crashes or other abnormalities occured during the entire time the system
was running. The system was shutdown normally using

"shutdown -h now"

At the conclusion of the shutdown the system was automatically powered off.

When I powered the system up later in the evening, the 36 gig drive failed
to mount. fsck reported that group 252 was incorrect, followed by numerous
other errors about dtime, and various bits that were not cleared. If you
want exact error messages please advise.

There is definitely a problem with large disk drives and linux unless I
have done something wrong (like use the wrong filesystem).

This problem is serious

An expeditious reponse would be greatly appreciated.

Comment 1 Bill Nottingham 1999-12-06 12:12:59 EST
Please enter all followup information on the *same* bug report.

*** This bug has been marked as a duplicate of 7506 ***

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