Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#537 - JFS mounted read only after crash

Attached to Project: Arch Linux
Opened by Pink Chick (Pink Chick) - Sunday, 14 March 2004, 08:34 GMT
Last edited by Judd Vinet (judd) - Sunday, 14 March 2004, 19:03 GMT
Task Type Bug Report
Category System
Status Closed
Assigned To Judd Vinet (judd)
Architecture not specified
Severity Critical
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 1
Private No

Details

After a system crash, jfs partitions are mounted read only - although fsck.jfs gives the feedback, the file system was checked and cleaned up.

Unluckily, if your root partition is running jfs, all daemons run into problems. It will take hours untill the system is booted up then, and you will find you can't fix anything. Remounting of / to get rid of read only fails.

As the system was unusable now, I made several tests with different fstab entries. Result: everytime the system is doing a hot restart to simulate a crash jfs partitions are unwritable, and if it is the root partition, it is your systems death. I tried it for ten times on each of two different machines.

I have no idea, what could be responsible for this behaviour, I used jfs as a very fast and stable fs in debian for a long time.
This task depends upon

Closed by  Judd Vinet (judd)
Friday, 02 April 2004, 01:15 GMT
Reason for closing:  Deferred
Comment by Judd Vinet (judd) - Sunday, 14 March 2004, 20:40 GMT
I've reproduced the issue on a test box here, and it appears that fsck.jfs will not repair a filesystem if /etc/mtab says it's mounted RW.

When the system crashes and boots up again, the old /etc/mtab is still there, indicating that the root fs is mounted RW (even though it's not). The initscripts cannot remove that file because they can't mount the root fs until it's been fsck'ed. So we have a catch-22 here.

The only way I've found to fix it is to reboot with the disks/CD and fsck.jfs the device from there. Then mount the root fs under /mnt and remove the /mnt/etc/mtab file. Then take out the disk/CD and reboot.

I'll look into the problem further, but it may be an upstream issue. I don't have an elegant fix at this time.

Loading...