Wayne,
Wayne Stallwood wrote:
One of our servers did a strange thing today.
Suddenly at about half 11 this morning it remounted / as read only, I have seen filesystems do this on boot when fsck was unable to repair something automatically but this happened with an uptime of 80 days.
[...]
I am going to run extended offline smart tests of the disks over the weekend when the machine is less busy, but in the meantime can somebody confirm that damaged filesystems remounting themselves as ro is normal behaviour and if so what detects and schedules this ?
from the mount man page in the ext2/3 options section:
errors=continue / errors=remount-ro / errors=panic Define the behaviour when an error is encountered. (Either ignore errors and just mark the file system erroneous and con- tinue, or remount the file system read-only, or panic and halt the system.) The default is set in the filesystem superblock, and can be changed using tune2fs(8).
You can use the dumpe2fs program to show you what the default behaviour on errors is set to in the superblock.
HTH
JD