Bug 53154 - RC2 destroys file systems
RC2 destroys file systems
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
7.3
i386 Linux
high Severity high
: ---
: ---
Assigned To: Arjan van de Ven
Brock Organ
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-09-04 13:36 EDT by Alan Cox
Modified: 2005-10-31 17:00 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-09-04 14:41:15 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Alan Cox 2001-09-04 13:36:59 EDT
Celeron 900 + 256Mb RAM
Intel i815 chipset
Onboard eepro100, video, audio, etc  [MX3S board]
ATP870U scsi present + m/o drive + scsi disk (not in use)
Promise supertrak 100 (disabled)
IDE (30Gb on hda - root fs, hdd is an hp cd-writer)

It runs 7.1 fine
It ran an earlier beta with a 2.4.6-3 kernel fine too
Loading RC2 hangs the box during the install trashing the file system when
doing an upgrade. We are talking mkfs grade trashing here.

I've run memtest86 on it - so far its totally clean
CPU temperature is good, voltage reports are good
Comment 1 Arjan van de Ven 2001-09-04 13:57:17 EDT
Would it be possible to see if 2.4.7-2 did this too ? (Roswell2)

That would be a very interesting inbetween point
Comment 2 Alan Cox 2001-09-04 14:41:11 EDT
I've got a few things to try once the test set finishes.

1. Running an upgrade to RC2 keeping the fs ext2 and doing it in text mode to
   look for exciting oops data

2. If that works then trying X11 with ext2 and vice versa.

Unfortunately its a slow process to go reinstalling/retesting so I dont want to
do too many 7.1 installs
Comment 3 Alan Cox 2001-09-04 15:55:35 EDT
Ok the critical factor is BIOS ACPI/APM enable. Seems the MX3S BIOS rev 1.11 is
not a happy object.

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