Ext3 users - Jun 2005 - [Q] Is errors=panic safe to use, and will it detect a RAID gone psycho?

I have had in years past seen hardware (SCSI) RAID controllers lose 
it electronically causing the kernel to fill the logs with scary SCSI 
messages and ext3 to complain about "holes" in the filesystem like so:

Sep  7 14:47:17 thewarehouse1 kernel: EXT3-fs error (device 
sd(8,81)): ext3_readdir: directory #376833 contains a hole at offset 0

I'm using drbd and heartbeat so whatever gets written to the hardware 
RAID gets written independently to a second RAID on a second 
computer. It would be nice if in the unlikely event hardware failed 
to cause something bad such as the one aforementioned to trigger the 
computer to fail entirely and force heartbeat/drbd to kick in on the 
second computer.

If I set the error behavior with tune2fs to panic, would this happen? 
That is, is this the type of error that would trigger a panic? Are 
there minor errors that could unnecessarily trigger one?
-- 

Maurice Volaski, mvolaski at aecom.yu.edu
Computing Support, Rose F. Kennedy Center
Albert Einstein College of Medicine of Yeshiva University

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Maurice Volaski schrieb:
> If I set the error behavior with tune2fs to panic, would this happen?
> That is, is this the type of error that would trigger a panic? Are there
> minor errors that could unnecessarily trigger one?
panic seems to be triggered in fs/ext3/super.c, there are some conditions
to met in ext3_handle_error() and ext3_abort(). either get a clue from
that or perhaps some ext2 guru can comment as to *when* exactly a panic is
triggered ;-)


- --
BOFH excuse #12:

dry joints on cable plug
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCxIw9C/PVm5+NVoYRAqVRAJ4iTIbmFvi1OoqqcZPyuFtzeo7OkQCg2fAO
kIOJsD6artMMh49BIYfj1Ks=thhq
-----END PGP SIGNATURE-----