Thanks, Chris. I ran e2fsck with the -c option, which runs badblocks, when I tested it earlier. And I just ran
badblocks again - 0 bad blocks found. I wish I could fix this by simply as swapping out a bad disk (notwithstanding
Andre's desire for intellectual pursuits), but I really think it's software, either in some service mucking up the JVM
or the JVM itself. But it only manifests itself under Tomcat, and then only when this particular package is imported.
Christopher Schultz wrote:
Sam and David,
On 2/20/2009 1:36 PM, David Smith wrote:
Sam Hokin wrote:
It's a logical RAID array on four physical disks. I've
run fsck on it (when this all first happened) and it's fine.
It _could_ be a disk issue. I've seen disks that scan fine contain a
growing number of blocks causing read errors and continuous retries.
Yeah, you gotta run badblocks on it. fsck just checks the filesystem
integrity, not the physical disk.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
