[opensuse] FS falling back to read-only
Hi, Since recently I experience problems with my root partition falling back at random to be read-only. mount still shows it mounted as rw: /dev/mapper/SYSTEM-ROOT on / type ext3 (rw,acl,user_xattr) creating anything on that FS fails: touch /tmp/test touch: cannot touch `/tmp/test': Read-only file system remounting it rw fails: sudo mount -o remount,rw / mount: block device /dev/mapper/SYSTEM-ROOT is write-protected, mounting read-only Rebooting the system solves it, until a random date / time when this is going to happen again. The disk was replaced (incl. cabling). Any ideas would be highly appreciated Dominique -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Dominique Leuenberger wrote:
Hi,
Since recently I experience problems with my root partition falling back at random to be read-only. mount still shows it mounted as rw: /dev/mapper/SYSTEM-ROOT on / type ext3 (rw,acl,user_xattr)
creating anything on that FS fails: touch /tmp/test touch: cannot touch `/tmp/test': Read-only file system
remounting it rw fails: sudo mount -o remount,rw / mount: block device /dev/mapper/SYSTEM-ROOT is write-protected, mounting read-only
Do an fsck before you remount it. Then check dmesg and/or your /var/log/messages. There has got to be an indication of why the filesystem is failing and going into RO mode. /Per -- Per Jessen, Zürich (-3.0°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2009-02-18 at 14:04 +0100, Per Jessen wrote:
Then check dmesg and/or your /var/log/messages. There has got to be an indication of why the filesystem is failing and going into RO mode.
Possibly it never gets written there, it is RO, which leaves dmesg. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkmcC1gACgkQtTMYHG2NR9W+aACfevwYkTKXY9HYUFXFezivQeYy rREAnjEbHl/abIUOqGNtJqO0LI4MWe+y =YUsI -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2/18/2009 at 2:21 PM, "Carlos E. R." <robin.listas@telefonica.net> wrote: On Wednesday, 2009-02-18 at 14:04 +0100, Per Jessen wrote:
Then check dmesg and/or your /var/log/messages. There has got to be an indication of why the filesystem is failing and going into RO mode.
Possibly it never gets written there, it is RO, which leaves dmesg.
No worries for that one :) /var is on an own volume and does not suffer from this read-only issue. a FS check (ext3) yielded some 'unlink' errors... they were fixed.. but it insists of rebooting the machine before remounting (yaiks). Will have to do this later in the evening (I know this machine does not come up when my external disk is connected to USB... and it is now of course). And the system is not where I am. Thanks anyway so far. Will give more debug from /var/log/messages tomorrow. Dominiqu -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Dominique Leuenberger wrote:
On 2/18/2009 at 2:21 PM, "Carlos E. R." <robin.listas@telefonica.net> wrote: On Wednesday, 2009-02-18 at 14:04 +0100, Per Jessen wrote:
Then check dmesg and/or your /var/log/messages. There has got to be an indication of why the filesystem is failing and going into RO mode.
Possibly it never gets written there, it is RO, which leaves dmesg.
No worries for that one :) /var is on an own volume and does not suffer from this read-only issue.
a FS check (ext3) yielded some 'unlink' errors... they were fixed.. but it insists of rebooting the machine before remounting (yaiks).
Really? Who insists on that? I've had similar problems before, and I've never had to reboot. JUst do the fsck, then remount. -- Per Jessen, Zürich (-2.0°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2009-02-18 at 14:42 +0100, Per Jessen wrote:
a FS check (ext3) yielded some 'unlink' errors... they were fixed.. but it insists of rebooting the machine before remounting (yaiks).
Really? Who insists on that? I've had similar problems before, and I've never had to reboot. JUst do the fsck, then remount.
Yes, when you do an automatic fsck of the root filesystem (via /etc/init.d/boot.rootfsck) it always (I think) reboots. It doesn't happen, I think, if the fsck is of an auxiliary filesystem (via /etc/init.d/boot.localfs) it doesn't reboot. The alternative is, of course, run the fsck from a rescue system, manually. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkmcFE8ACgkQtTMYHG2NR9VGTQCfemYHaNMYnDCivcgCEijxJenJ vmQAn3Aa+7ctJrmEXtL/2X9+1iUtQldR =Sn6n -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. wrote:
On Wednesday, 2009-02-18 at 14:42 +0100, Per Jessen wrote:
a FS check (ext3) yielded some 'unlink' errors... they were fixed.. but it insists of rebooting the machine before remounting (yaiks).
Really? Who insists on that? I've had similar problems before, and I've never had to reboot. JUst do the fsck, then remount.
Yes, when you do an automatic fsck of the root filesystem (via /etc/init.d/boot.rootfsck) it always (I think) reboots.
Well, I was thinking of just doing an fsck, nothing automatic or otherwise. fsck /dev/xxxx mount -o remount,rw / It's been a while since I've had to do it, but I feel pretty certain fsck didn't say anything about rebooting. I could be wrong though. /Per -- Per Jessen, Zürich (-2.6°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2/18/2009 at 3:24 PM, Per Jessen <per@opensuse.org> wrote: Well, I was thinking of just doing an fsck, nothing automatic or otherwise.
fsck /dev/xxxx mount -o remount,rw /
It's been a while since I've had to do it, but I feel pretty certain fsck didn't say anything about rebooting. I could be wrong though.
That's the way I did it... fsck.ext3 /dev/... It said at the end that LINUX NEEDS TO BE REBOOTED mount -o remount,rw / refused to remount it rw... that's why I concluded to do a reboot this evening Dominique -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2009-02-18 at 15:26 +0100, Dominique Leuenberger wrote:
On 2/18/2009 at 3:24 PM, Per Jessen <per@opensuse.org> wrote: Well, I was thinking of just doing an fsck, nothing automatic or otherwise.
fsck /dev/xxxx mount -o remount,rw /
It's been a while since I've had to do it, but I feel pretty certain fsck didn't say anything about rebooting. I could be wrong though.
That's the way I did it... fsck.ext3 /dev/... It said at the end that LINUX NEEDS TO BE REBOOTED mount -o remount,rw /
refused to remount it rw...
Yes, because you are fsck-ing the root filesystem of the currently running system, and there have been changes. Otherwise you could have umounted-remounted without a reboot. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkmcMhwACgkQtTMYHG2NR9WVogCbB6TElddE7uNdqEa5PexmrHI+ KFQAniC0uQ31sKb81SnrLN3MdWBojjTJ =a9nd -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2/18/2009 at 2:42 PM, Per Jessen <per@opensuse.org> wrote: Dominique Leuenberger wrote:
Really? Who insists on that? I've had similar problems before, and I've never had to reboot. JUst do the fsck, then remount.
FSCK told me to do so and a remount still does not work... so I guess it likes having this reboot. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Dominique Leuenberger wrote:
On 2/18/2009 at 2:42 PM, Per Jessen <per@opensuse.org> wrote: Dominique Leuenberger wrote:
Really? Who insists on that? I've had similar problems before, and I've never had to reboot. JUst do the fsck, then remount.
FSCK told me to do so and a remount still does not work... so I guess it likes having this reboot.
Haha, yes - maybe it's filesystem dependent? /Per -- Per Jessen, Zürich (-2.2°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday February 18 2009, Per Jessen wrote:
Dominique Leuenberger wrote:
On 2/18/2009 at 2:42 PM, Per Jessen <per@opensuse.org> wrote:
Dominique Leuenberger wrote:
Really? Who insists on that? I've had similar problems before, and I've never had to reboot. JUst do the fsck, then remount.
FSCK told me to do so and a remount still does not work... so I guess it likes having this reboot.
Haha, yes - maybe it's filesystem dependent?
I think it's because it's the root file system that was fixed.
/Per
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (4)
-
Carlos E. R. -
Dominique Leuenberger -
Per Jessen -
Randall R Schulz