Well, actually i MIGHT have found the solution of this problem, or better, the cause. On my system suspend/resume doesn't work, so some times I try to see if this is fixed and, when resuming, the system hangs, and the only solution is a hard reboot. When doing that the filesystem is dirty and hence need to be fscked. The problem is that sometimes I turn up the machine of the mains, and so fsck is not being executed (which I think is pretty silly). When the filesystem is dirty jfs refueses to mount the filesystem as r/w and mounts it only as r/o.
The solution, for me, is to run fsck on the readonly root and then reboot the system. Last time this happened this solved the problem. But I'll leave this bug open because fsck should be run even when on batteries. Hope this helps your problem. -- Jaunty: jfs filesystem being mounted read-only https://bugs.launchpad.net/bugs/361023 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
