Mailinglist Archive: opensuse-bugs (2150 mails)

< Previous Next >
[Bug 873919] New: root file system should not get mounted ro when fsck failes with uncorrected errors
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Wed, 16 Apr 2014 10:52:58 +0000
  • Message-id: <bug-873919-21960@http.bugzilla.novell.com/>

https://bugzilla.novell.com/show_bug.cgi?id=873919

https://bugzilla.novell.com/show_bug.cgi?id=873919#c0


Summary: root file system should not get mounted ro when fsck
failes with uncorrected errors
Classification: openSUSE
Product: openSUSE 13.1
Version: Final
Platform: x86-64
OS/Version: openSUSE 13.1
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Basesystem
AssignedTo: bnc-team-screening@xxxxxxxxxxxxxxxxxxxxxx
ReportedBy: thomas.blume@xxxxxxxx
QAContact: qa-bugs@xxxxxxx
Found By: Development
Services Priority: 1000
Blocker: ---


/lib/mkinitrd/boot/83-mount.sh

contains the following code snipped:

elif [ $ROOTFS_FSCK -gt 3 ] ; then
echo "fsck failed. Mounting root device read-only."
read_only=1


According to the fsck manpage fsck return code 4 is:

4 - File system errors left uncorrected

On my machine, fsck exited with code 4 and system root was mounted readonly:

-->--
fsck from util-linux 2.23.2
[/sbin/fsck.ext4 (1) -- /] fsck.ext4 -a /dev/mapper/root
/dev/mapper/root: One or more block group descriptor checksums are invalid.
FIXED.
/dev/mapper/root: Group descriptor 16 checksum is 0x4b1a, should be 0x50e6.

/dev/mapper/root: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
+++ ROOTFS_FSCK=4
+++ export ROOTFS_FSCK
+++ mkdir /run/initramfs
+++ echo 4
+++ ROOTFS_FSTYPE=ext4
+++ export ROOTFS_FSTYPE
+++ '[' 4 -gt 1 -a 4 -lt 4 ']'
+++ '[' 4 -gt 3 ']'
+++ echo 'fsck failed. Mounting root device read-only.'
fsck failed. Mounting root device read-only.
+++ read_only=1
+++ opt='-o rw'
+++ '[' 1 ']'
+++ opt='-o ro'
+++ echo 'Mounting root /dev/root'
Mounting root /dev/root
+++ '[' ext4 = xfs -a -n '' ']'
+++ '[' ext4 = reiserfs -a -n '' ']'
+++ '[' -n '' ']'
+++ '[' -n acl,user_xattr ']'
+++ opt='-o ro,acl,user_xattr'
+++ '[' -n ext4 ']'
+++ opt='-o ro,acl,user_xattr -t ext4'
+++ echo mount -o ro,acl,user_xattr -t ext4 /dev/root /root
mount -o ro,acl,user_xattr -t ext4 /dev/root /root
+++ mount -o ro,acl,user_xattr -t ext4 /dev/root /root
[ 20.145236] EXT4-fs (dm-0): ext4_check_descriptors: Checksum for group 16
failed (20710!=19226)
[ 20.231110] EXT4-fs (dm-0): ext4_check_descriptors: Checksum for group 32
failed (3769!=5445)
[ 20.371701] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts:
acl,user_xattr
--<--

This leaves me with an unusable system after some systemd services fail due to
the readonly root.
I don't see any sense in mounting the root fs ro when fsck fails with
uncorrected errors.
The initrd should rather not mount it and go into an emergency shell.

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

< Previous Next >