When I ran fsck after the first bout of failure, it did report a lot of errors. I do not have a copy of that fsck transcript; however, I have not yet run fsck since my second attempt. Is there a method of capturing the transcript that is preferred? Bryan From: Ted Ts'o <tytso@xxxxxxx> To: bryan.coleman@xxxxxxxx Cc: linux-ext4@xxxxxxxxxxxxxxx Date: 02/07/2011 05:55 PM Subject: Re: ext4 problems with external RAID array via SAS connection Sent by: linux-ext4-owner@xxxxxxxxxxxxxxx On Mon, Feb 07, 2011 at 01:53:18PM -0500, bryan.coleman@xxxxxxxx wrote: > I am experiencing problems with an ext4 file system. > > At first, the drive seemed to work fine. I was primarily copying things > to the drive migrating data from another server. After many GBs of data, > that seemingly successfully were done being transferred, I started seeing > ext4 errors in /var/log/messages. I then unmounted the drive and ran fsck > on it (which took multiple hours to run). I then ls'ed around and one of > the areas caused the system to again throw ext4 errors. Did fsck report any errors? Do you have a copy of your fsck transcript? The errors you've reported do make me suspicious that there's something unstable with your hardware... - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
