Scott Waller <[email protected]> writes:
> mmmm.....I think your right. I have looked through the syslog and couldn't
> find any issues, but now you've got me worried. Anyway I did a backup last
> night. Seems to be quite stable at the moment.
If you are, just 'touch /forcefsck' as root, reboot, and the distribution
should check the filesystems for errors — which will catch any problems.
> I wonder if when I passed the:
> sudo mount -o remount, rw /
> Then it wrote that to the /etc/fstab file??
No. None of the traditional Unix tools modify fstab, and certainly not
mount. It might have come from a typo, or an administrative (usually GUI)
tool, but not from there.
> and in my panic just missed it.
> What other things would cause a EXT3 file system to go into read only?
Remounting 'ro' explicitly, dropping to the file system early enough in the
boot process that it has not remounted to 'rw' yet, or corruption.
Daniel
--
✣ Daniel Pittman ✉ [email protected] ☎ +61 401 155 707
♽ made with 100 percent post-consumer electrons
Looking for work? Love Perl? In Melbourne, Australia? We are hiring.
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
