On Wed, Apr 3, 2013 at 11:43 PM, gregrwm <tclug1 at whitleymott.net> wrote: > i routinely specify errors=remount-ro for all mountpoints in fstab. well > i'm guessing it must've finally actually just happened. i got a few rsync > command errors like > > rsync: mkstemp "/vp/201/var/nagios/spool/checkresults/.checkzXAdNO.u4thPb" > failed: Read-only file system (30) > rsync: mkstemp "/vp/201/var/nagios/spool/checkresults/.checkzfSgt2.TEekFF" > failed: Read-only file system (30) > rsync: mkstemp "/vp/201/var/run/.utmp.rddpv9" failed: Read-only file > system (30) > > so i check /proc/mounts and whaddyaknow it's mysteriously become > readonly. but i'm very surprised to find nothing unusual in > /var/log/messages. and /proc/mdstat is all UU's. > > i was just about to migrate containers onto this box. it was fine last > week. well heck, better run some tests instead i guess. but what? if it > wasn't raid1/lvm, i'd run fsck -c, but as it is raid1/lvm, what should i > bang on it with? > > Another thought is that you can try bringing up the system as a degraded RAID1 and try each disk to see which one is failing. -- http://mtu.net/~jpschewe -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mailman.mn-linux.org/pipermail/tclug-list/attachments/20130405/56a6d973/attachment.html>