It seems that ext3 journalling doesen't agree with my mobo's HPT66 UDMA controller. The motherboard is a dual Celeron 333, Abit-BP6 from memory.
As near as I can tell, when I'm performing mass updates like deleting the contents of a large directory the journal code goes gaga and triggers some sort of exception and remounts the filesystem readonly. This was happening with kernel 2.4.7, 2.4.9 and now 2.4.18 on my RedHat 7.2 / now 7.3 box. Lucky for me it doesen't contain the root filesystem (/home and /arch1) As the box is in Newcastle and I'm in Sydney I wanted to be able to login via SSH no matter what so I've done a couple of nifty hacks to the startup. a) I've set /home and /arch1 to no check and no auto mount in /etc/fstab. I've made a script /etc/rc.d/init.d/mounthome and inserted it in the startup sequence after SSH but before NFS. It's purpose is to do the usual filesystem checks, but if there's any error it gives up & just mounts them readonly. b) Just in case, I've moved the startup of mingetty on tty2 up to just after rc.sysinit in /etc/inittab which means if the startup sequence hangs somewhere you can still login on tty2. I'm going to impliment this last one on our office servers because they all seem to go a bit haywire with our NFS setups. I also think there's some weird hub/nic issues causing startup difficulties. -- ---<GRiP>--- Grant Parnell - senior consultant For all your Linux Commercial quality support and consulting needs Web: http://www.linuxhelp.com.au Email: [EMAIL PROTECTED] For retail sales see http://www.everythinglinux.com.au Phone 02 8753 0792 to book service. -- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
