On 06/05/2017 07:40 PM, Andrey Ryabinin wrote:
From: Dmitry Monakhov <[email protected]>*Purpose: It is reasonable to annaunce fs related events via uevent infrastructure. This patch implement only ext4'th part, but IMHO this should be usefull for any generic filesystem. Example: Runtime fs-error is pure async event. Currently there is no good way to handle this situation and inform user-space about this. *Implementation: Add uevent infrastructure similar to dm uevent FS_ACTION = {MOUNT|UMOUNT|REMOUNT|ERROR|FREEZE|UNFREEZE} FS_UUID FS_NAME FS_TYPE Signed-off-by: Dmitry Monakhov <[email protected]> h + /* Deal with the reporting of failure conditions on a filesystem such as * inconsistencies detected or read IO failures. * @@ -411,6 +485,7 @@ static void ext4_handle_error(struct super_block *sb) if (test_opt(sb, ERRORS_PANIC)) panic("EXT4-fs (device %s): panic forced after error\n", sb->s_id); + ext4_send_uevent(sb, EXT4_UA_ERROR);
Pls make high rate protection for EXT4_UA_ERROR. It would be great to emit single fserror event on remount to RO -- Igor. _______________________________________________ Devel mailing list [email protected] https://lists.openvz.org/mailman/listinfo/devel
