[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Bad directories appearing in ext3 after upgrade 2.4.16 ->2.4.18+cvs

I'm the person who wrote the post with the "ominous end" referenced
below.. I've since stopped using a md raid1 ext3 root partition, but
still use md raid1 home partitions without any trouble.

One thing that I discovered after making this change is that the IDE
drives (Seagate Barracuda IV, 7200RPM, ATA-100) I'm using in the md
array enable write-caching by default. I disabled this with hdparm and
noticed a significant decrease in performance, especially when
resynchronizing the md array after an unclean shutdown. Still, it would
appear that this is the right thing to do if you want to have the best
chance of surviving a power hit.

I don't know if the write-caching on the drives was in any way related
to the problems I saw trying to fsck the md raid1 ext3 root partition,
but I thought I would mention it.


On Tue, 2002-05-21 at 13:49, Andreas Dilger wrote:
> On May 21, 2002  16:30 +1000, Neil Brown wrote:
> >  My ext3 filesystem is on a raid5 array, with the journal on
> >  a separate raid1 array. (data=journal mode).
> Just to follow up on my previous email, the "other ext3/RAID problems"
> are probably from the thread below (start, and ominous end):
> http://marc.theaimsgroup.com/?l=ext3-users&m=101489319820233&w=4
> http://marc.theaimsgroup.com/?l=ext3-users&m=102011493526790&w=4
> In his case, running e2fsck on the MD RAID filesystem actually
> causes corruption that wasn't there before (see last message)...
> Cheers, Andreas
> --
> Andreas Dilger
> http://www-mddsp.enel.ucalgary.ca/People/adilger/
> http://sourceforge.net/projects/ext2resize/
> _______________________________________________
> Ext3-users mailing list
> Ext3-users redhat com
> https://listman.redhat.com/mailman/listinfo/ext3-users

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]