[Ocfs2-users] Can you reboot instead of remounting a ocfs FS as RO?

[Sunil Mushran]

# mount -o errors=panic ....

Listed in mount.ocfs2's manpage.

       errors=remount-ro / errors=panic
              Define the behavior when an error is encountered. (Either 
remount the file system read-only, or panic and halt
              the system.) By default, the file system is remounted read 
only.


David Murphy wrote:
>
> I got this  today:
>
>  
>
>  
>
> Nov 19 04:43:04 rgapp1 kernel: OCFS2: ERROR (device sdb1): 
> __ocfs2_find_path: Inode 2845006 has empty extent list at depth 1
>
> Nov 19 04:43:04 rgapp1 kernel:
>
> Nov 19 04:43:04 rgapp1 kernel: File system is now read-only due to the 
> potential of on-disk corruption. Please run fsck.ocfs2 once the file 
> system is unmounted.
>
> Nov 19 04:43:04 rgapp1 kernel: (2521,1):ocfs2_commit_truncate:6534 
> ERROR: status = -30
>
> Nov 19 04:43:04 rgapp1 kernel: (2521,1):ocfs2_truncate_for_delete:564 
> ERROR: status = -30
>
> Nov 19 04:43:04 rgapp1 kernel: (2521,1):ocfs2_wipe_inode:735 ERROR: 
> status = -30
>
> Nov 19 04:43:04 rgapp1 kernel: (2521,1):ocfs2_delete_inode:976 ERROR: 
> status = -30
>
> Nov 19 05:03:00 rgapp1 auditd[1981]: Audit daemon rotating log files
>
> Nov 19 05:24:18 rgapp1 kernel: OCFS2: ERROR (device sdb1): 
> __ocfs2_find_path: Inode 2845006 has empty extent list at depth 1
>
>  
>
>  
>
>  
>
> I wanted to know is there a way I can tell ocfs2  to cause a 
> opps/panic   on  FS errors like this to force a reboot?
>
>  
>
>  
>
> David Murphy
>