Hi, normally we do use write back cache on the RAID (which is backed up by battery so should be ok...) but in order to verify this isn't the cause we switched to write-through and it didn't help. The best behaviour I've seen so far was when I configured DATA=JOURNAL, but even then it's all very timing-sensitive and I still get writes/closes which finish ok but are not on the disk later on... And I've yet to see a real explanation/coverage of how journalling filesystems in general, and EXT3 specifically, handle disk failure situations like power loss or FC cable disconnection. Currently our direction is to monitor the loop state (via /proc) and initiate a killall on the application and umount once we see a loop down indication. A brute-force test of this mechanism seems to work... Anyhow thanks for the sugggestion, will be happy to continue experimenting. Yuval -----Original Message----- From: Robert Liu [mailto:rgliu@sr5tech.com] Sent: Friday, February 14, 2003 8:13 AM To: ext3-users@redhat.com Cc: Yuval Yeret Subject: RE: Lost writes upon disk power failure Response to the following posting: http://www.redhat.com/mailing-lists/ext3-users/msg09093.html Hi Yuval, Do you know if write back cache is enabled on the disks? If so, the problem you're observing maybe due to lost data in the cache when you powered down the RAID array. We've performed power cycle experiments on IDE RAID arrays and have observed similar problems: http://www.sr5tech.com/write_back_cache_experiments.htm Rob ------------------------------------------------------------ Robert Liu Boon Storage Technologies, Inc. rgliu@sr5tech.com (408)393-8998 www.sr5tech.com ------------------------------------------------------------ _______________________________________________ Ext3-users@redhat.com https://listman.redhat.com/mailman/listinfo/ext3-users
