On Thu, 2006-10-26 at 17:41 +0000, Dave Kleikamp wrote: > I would suspect that this is only happening after an unclean shutdown. > I am curious what would be triggering a full check. Is phase 0 failing? > This may be a bug. jfs_fsck keeps a log of its most recent run. You > can extract it with the command, "jfs_fscklog -d -e /dev/<device> -f > <output file>" and send that file to me. (You don't need to cc the > list.) If the last boot was clean, this won't help, so you'll need to > wait until it does the full check again.
Thanks for the info. I'll do that next time we believe a boot was delayed due to a JFS fsck. However, we may have found the cause of our problem, which is elsewhere. When our systems are run in developer mode, they write lots of data to /var/tmp, which is currently ext3. This partition will get force-fscked every 30 days and this may explain the long boot delays we were seeing. Thanks! Daniel ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Jfs-discussion mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jfs-discussion
