On Fri, 08 Sep 2006 16:32:57 +1200
"Davidson, Brett (Managed Services)" <[EMAIL PROTECTED]> wrote:
> Ahh - thought as much. :-) Whilst I did get an exposure to Sys5 from
> Christopher Sawtell (whilst he still had Gerty) I didn't get down that
> far into the depths of the beast.
>
> No - haven't played with maxbpg . Would be quite useful with large files
> but all of the environments that I support that have files large enough
> to be contenders for this, raw device acces is used, making the option
> somewhat moot.
> Not sure how it would help me in this circumstance.
-e error-behavior
Change the behavior of the kernel code when errors are detected.
In all cases, a filesystem error will cause e2fsck(8) to check
the filesystem on the next boot. error-behavior can be one of
the following:
continue Continue normal execution.
remount-ro Remount filesystem read-only.
panic Cause a kernel panic.
Thought it might force the command to complete, and then allow e2fsck to work
without using the journals.
