I fsck'd it and it seems to be in pretty good shape. This is 2.4.18 - RH9. This machine can't handle file system problems. It has to stay RH9 but I could back out the journalling. The machine is only 3 months old. I don't think it's a hardware issue. No error messages and the symptom (aside from being unusable) was I/O error seeking <different blocks>. The fsck unloaded the journal (about 6 entries for the tomcat user on /home and about a dozen for root on /usr) and a later preen seemed to take a long time on those partitions. I don't see that I lost anything although the databases aren't coming up. Thoughts? similar experiences? I'd like to know what else I could do to both find the problem source and to make sure I lose as little as possible when recovering. I used e2image -r and ran the fsck on it to make sure I knew what it was going to do. But I don't know anything really about the problem area. What else would be a good thing to try? Dana Bourgeois
On Wed, Oct 01, 2003 at 11:54:10PM -0700, Dana Bourgeois wrote:> I fsck'd it and it seems to be in pretty good shape. This is 2.4.18 - RH9. > This machine can't handle file system problems. It has to stay RH9 but I > could back out the journalling. > > The machine is only 3 months old. I don't think it's a hardware issue. No > error messages and the symptom (aside from being unusable) was I/O error > seeking <different blocks>.Absolutely no messages in your log files? There really should have been some, unless the filesystem that went read-only when the filesystem error occured was where your logs are being kept? Two things I can think of trying: First of all, make sure you have the lasted errata kernel from Red Hat installed. Secondly, consider doing network-based syslogging (i.e., configure syslog.conf to send its logs over the network to a logging server). I generally consider that to be a really good idea for production servers. - Ted