If you have poorly written software which corrupts your file system e.g. during its installation, you probably face the problem that once the error occurs, the filesystem will lock for writing, and then your installation suddenly dies, hopeless.
Well, in the case that you want to force it to continue, even after (it) having broken your file system, you can, if it is in the EXT family (EXT2, EXT3 filesystems). The command is (as root) this:
tune2fs -e continue device
device is the one device this option is going to be applied.
Then, after the next reboot, e2fsck (file system check) will check the error, anyway, so you are “safe”. I had two situations installing poorly written software (I hope only the installer is poor in quality), and it helped going on until the end. One of them uses file system intensively and did not present any errors during production execution.
This is analogous to the mount command’s option errors (mount -o errors=continue). Or it can also be one of the options field’s values, in the fstab file e.g. “defaults,errors=continue“.
