Bug 10375 - Mageia does not handle btrfs filesystem errors correctly on boot
Summary: Mageia does not handle btrfs filesystem errors correctly on boot
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 3
Hardware: i586 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-31 14:31 CEST by Joseph Wang
Modified: 2015-03-31 16:05 CEST (History)
0 users

See Also:
Source RPM: btrfs-progs
CVE:
Status comment:


Attachments

Description Joseph Wang 2013-05-31 14:31:29 CEST
Description of problem:

When mageia sees a file system error in btrfs running fsck.btrfs it just stops.  There is no command line allowing the user to run btrfsck to clear the error.

Version-Release number of selected component (if applicable):


How reproducible:

Every time there is a filesystem error


Steps to Reproduce:
1. Shut down btrfs uncleanly
2. boot up mageia
3. The mageia boot will get stuck with btrfs


Reproducible: 

Steps to Reproduce:
Comment 1 Joseph Wang 2013-06-02 21:09:43 CEST
The problem is a crash in btrfsck.  When btrfsck encounters an error, the fsck crashes from an internal error, and the boot stops.  The filesystem is ok in that simply mounting the filesystem works.

Will try to see if a newer btrfs-prog will work better.
Comment 2 Marja Van Waes 2015-03-31 16:05:08 CEST
Mageia 3 changed to end-of-life (EOL) status 4 months ago.
http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ 

Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD


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