Mailinglist Archive: opensuse-bugs (4060 mails)

< Previous Next >
[Bug 508619] New: Constant file system corruption
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Mon, 1 Jun 2009 02:24:52 -0600
  • Message-id: <bug-508619-21960@xxxxxxxxxxxxxxxxxxxxxxxx/>
http://bugzilla.novell.com/show_bug.cgi?id=508619


Summary: Constant file system corruption
Classification: openSUSE
Product: openSUSE 11.2
Version: Milestone 2
Platform: x86-64
OS/Version: SuSE Other
Status: NEW
Severity: Critical
Priority: P5 - None
Component: Kernel
AssignedTo: bnc-team-screening@xxxxxxxxxxxxxxxxxxxxxx
ReportedBy: pBakhuis@xxxxxxxxx
QAContact: qa@xxxxxxx
Found By: ---


User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.10)
Gecko/2009042700 SUSE/3.0.10-3.1 Firefox/3.0.10

The system in question is using a foxconn a7gm-s motherboard with the AMD 780G
chipset and an Athlon 1640-LE CPU, the (root) disk is partioned as ext4.

After installing milestone 2(fresh install) and using the default repositories
/ running an update and rebooting the system afterwards the system becomes
unusuable. I'll be notified the filesystem has become corrupt and can run fsck
to no avail as the system unusuable and the root partition will be mounted as
read only/unable to boot.

I've also tried Ubuntu 9.04 where the problem seems even worse and the very
first boot leads to read-only mounted root partition.

I've had a similar with openSUSE 11.1 and milestone 1 (using ext3 instead of
ext4 however) where the filesystem would sometimes upon rebooting become
corrupt (the longer the system has been running the bigger chance it will cause
problems). This however was nearly always fixable by running fsck (sometimes it
would revert the ext3 to ext2).
As the behaviour in 11.1/11.2 milestone 1 was random I can't say with certainty
but I think the reiser filesystem might last longer although in time it did
have the same problem...
The errors fixed by fsck are always of the type "multiply claimed blocks".

Reproducible: Always

Steps to Reproduce:
1. Install operating system
2. Enable default repositories
3. Run updates
4. Reboot
Actual Results:
Warning about filesystem being corrupt and needing to run fsck manually.

Expected Results:
A working desktop

http://pastebin.com/f7cb7280d Start up log upon first boot after the install

--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >
This Thread
  • No further messages