On Mon, 3 Jan 2005, Morten Sylvest Olsen wrote: > > So to the upper layers, ext3, userland, etc. that should look like a > > catastrophic hardware failure -- anything trying to read/write to it > > should (IMO) have simply returned with IO errors. > > That depends on the options when the filesystem was mounted. Or the > options set in the superblock. The choices are continue, remount > read-only or panic. however - on the system in question: xena:/home/gordonh# dumpe2fs -h /dev/md5 ... Errors behavior: Continue ... and there are no mount options to say otherwise. There are lots of ext3 whinges in the log-file so I guess it just got fed-up... And this really isn't a linux-raid issue, just something I noticed recently to do with ext3... I did try XFS a while back, but had more problems with it and no satisfactory answers, so gave up on it... The trouble is, you get too used to what works and tend to stick with it... Ah well. Gordon - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
