Doesn't work that way. If there are inconsistencies between the two disks in the RAID1 array, it's handled by the RAID controller, not by the fsck. ----- Original Message ----- From: "Michael Wright" <mikewright@xxxxxxxxxxxxxx> To: <ataraid-list@xxxxxxxxxx> Sent: Monday, August 19, 2002 5:23 AM Subject: Question about using FAT32 with ataraid and Promise FT100 > Hey all, > > If I have the following setup: > > - Kernel 2.4.18 > - 2 x Western Digital 80GB IDE Drives > - RAID 1 setup through Promise BIOS. > - ataraid.o and pdcraid.o loaded at startup. > - Formatted /dev/ataraid/d0p0 as FAT32. > - Mounted /dev/ataraid/d0p0 on /mnt/raid > > Now here is the scenario: > > 1. A file is created on /mnt/raid (say "cp /var/log/messages /mnt/raid") > 2. The power is switched off on the box a point such that the FATs (File > Allocation Tables) are out of sync. > > My question is: > How can DOSFSCK fix the raid array (/dev/ataraid/d0p0)? > > Since the FATS are out of sync and that reads are balanced across the > disks, when dosfsck try's to read the FATs to find out what state they > are in, it will get different FATs each time it is run. This could cause > it to further stuff-up the FATs. > > Has anyone had any experience with this? > > Mike. > > > > > _______________________________________________ > > Ataraid-list@xxxxxxxxxx > https://listman.redhat.com/mailman/listinfo/ataraid-list >
