How to set panic option when ext3 file system sees errors.

Solution Unverified - Updated -

Environment

  • Redhat Enterprise Linux 5.3
  • ext3

Issue

  • SAN boot Server does not panic, when it lost connection to SAN.
  • System does not panic in case file system goes to read only status.

Resolution

  • In order for system to panic in situations when file system goes to read only status, it is necessary to mount file systems with below option in /etc/fstab.
errors=panic

From man mount we see what options are available and how file system will react in case of file system errors.


errors=continue / errors=remount-ro / errors=panic Define the behaviour when an error is encountered. (Either ignore errors and just mark the file system erroneous and continue, or remount the file system read-only, or panic and halt the system.) The default is set in the filesystem superblock, and can be changed using tune2fs(8).

Root Cause

errors=panic was not set as mount option for ext3 or ext4 system.

Diagnostic Steps

System will report that it goes to read only mode,but will not panic. Having system to panic on read only state in combination with kdump/vmcore can help to find out root cause for read only state.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Comments