Comment 59 for bug 672177
Revision history for this message
| Clint Byrum (clint-fewbar) wrote Re: [Bug 672177] Re: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted | #59 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
On Sun, 2011-01-23 at 12:39 +0000, ingo wrote:
> Observed just another oddity, probably a separate bug in mountall?
>
> I tried to mount the / filesystem (ext3) in journal mode to see if this improves the situation by adding the option to /etc/fstab:
> data=journal,
> But that results in boot process stalling with / filesystem mounted ro and just a console. dmesg | grep -i ext3 tells me:
>
> EXT3-fs: mounted filesystem with ordered data mode
> EXT3-fs (device sda1): Cannot change data mode on remount. The filesystem is mounted in data=ordered mode and you try to remount it in data=journal mode.
>
> The only way out and to continue boot-up is to manually remount the fs rw by:
> mount -o remount,rw /dev/sda1 /
> and remove the data=journal option from fstab.
>
Ingo, I believe changing the journalling of the root fs in this way is a
long standing issue with ext3/ext4, and has nothing to do with the libc6
issue. IIRC, it is only changeable by unmounting the fs, setting it, and
then mounting/unmounting again.