I've reproduced a possible EXT3/my journal problem on Redhat 7.2 (and maybe other versions).
After doing a full Redhat install, set up data=journal (default is ordered mode) in fstab. eg: LABEL=/ / ext3 defaults,data=journal 1 1 LABEL=/boot /boot ext3 defaults,data=journal 1 2 /dev/hdb2 /backup ext3 defaults,data=journal 0 2 Enable SysRq: echo 1 > /proc/sys/kernel/sysrq Sync the disks with Ctrl+Alt+SysRq+S. Then reboot. Upon reboot, you will find that the root file system gets mounted read-only, and all sorts of problems occur eg. anything that requires writing to /var or /dev, syslogger stalls, gettys can't respawn etc. I tried to use data=writeback in single-user mode, and try to shutdown and reboot cleanly without success. I also tried to pass "linux read-write" and even setup read-write in lilo.conf without success. The only way I can perform an unattended reboot is to use the "noload" option in fstab (ie. Do not load the ext3 file system's journal on mounting). I noticed that Redhat mounts the root file system in data=ordered mode before kudzu. I think it's mounting the ramdisk at this stage of bootup and bears little affect on the real root file system ... Does anybody know of a solution to this problem or have any suggestions, that will allow me to do unattended reboots while using data=journal ? ie. have things the way it was originally. Searched Google & redhat.com for keywords like sync, sysrq, redhat, ext3 etc without turning up any useful results. -- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
