1

Mounted filesystem / changed to read-only

view story
linux-howto

http://serverfault.com – This is how / should be mounted mount /dev/md0 on / type ext3 (rw,errors=remount-ro) but in fact, it is mounted read-only because of unknown reason so far for me. cat /proc/mounts /dev/md0 / ext3 ro,relatime,errors=remount-ro,data=ordered 0 0 :/var/log# echo aaa > /tmp/ddd bash: /tmp/ddd: Read-only file system As ext3 has errors=remount-ro flag, the possible reason is that the filesystem has errors. When I checked syslog/messages/dmesg I did not find any related information (no disk failures, filesystem errors etc.). This server does not have any iLo or so. So what do you recommend, (HowTos)

taskli's picture
Submitted by taskli on 08/20/2012

Stories similar to Mounted filesystem / changed to read-only

I'm trying to do the same of this question (multiple linux installation on same filesystem) but I get this result (root filesystem mounted as read-only) . I'm using debian/sid, have successfully modified the initrd /init script and patched the busybox switch_root to chroot into a subdirectory, the filesystem is ext4. The kernel boot but the filesystem is mounted read-only and any variant of mount

Let's say you have a btrfs root filesystem on an online system. You want to revert the filesystem to an earlier state, of which you have a snapshot:

remount /dev/sdaX / -o remount,subvol=snapshots/Y

For the record, I've done this in a test system, and it does not work.

Let's say you have a btrfs root filesystem on an online system. You want to revert the filesystem to an earlier state, of which you have a snapshot:

remount /dev/sdaX / -o remount,subvol=snapshots/Y

For the record, I've done this in a test system, and it does not work.

I was running a new script and encountered the following error:

Your filesystem or build does not support posix ACLs

So I thought no problem, just add acl,user_xattr to my fstab.

I'm running the lastest Ubuntu 12.04 AMI (ami-a29943cb) from Canonical on Amazon EC2 and quite often when I log in I get the message:

*** /dev/xvda1 will be checked for errors at next reboot ***

I have read a bunch of documentation on this and seem to understand that every so many reboots (around 37 see Mount count / Maximum mount count below) Ubuntu wants to check a disk for errors.

Hello all, perhaps this is an odd request, but I have the requirement none the less. Every time I mount a filesystem (at least an ext4 filesystem), I get a line indicating such in the syslog:

Oct 9 22:26:28 sulaco kernel: EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts:

I would like to not have these in the syslog.

I think my question is related to udev and/or udisks, but I am really not sure at all what's going on here. To start with, my system works more or less fine. The less part is due to the fact that, after some upgrades to my Debian install, the /dev folder started acting weird, in relation to what I used to think I knew about unix drive management.

I have a partition which won't mount, and keeps giving errors on every command I try.

Patient history: - was on a dualboot machine with most of the HD space dedicated to windows. - As I started to use linux more I ran out of space and used gparted to shrink the windows partition and get an extra linux partition. - formatted as ext3.

Ext3 is a journaled file system and maintains a journal file to prevent instances of metadata corruption due to unexpected power outage. Due to its wide testing base and relative simplicity, the file system is considered to be safer than its counterparts. But it is not completely immune to crashes.