Theodore Ts'o wrote:
> If the resize operation fails in the middle of the operation, mark the
> filesystem as needing to be checked, and tell the user that they
> should run e2fsck -fy on the device.
>
> Signed-off-by: "Theodore Ts'o" <tytso@xxxxxxx>
Good plan.
Reviewed-by: Eric Sandeen <sandeen@xxxxxxxxxx>
> ---
> resize/main.c | 7 ++++++-
> 1 files changed, 6 insertions(+), 1 deletions(-)
>
> diff --git a/resize/main.c b/resize/main.c
> index 2dae161..990a967 100644
> --- a/resize/main.c
> +++ b/resize/main.c
> @@ -455,7 +455,12 @@ int main (int argc, char ** argv)
> if (retval) {
> com_err(program_name, retval, _("while trying to resize %s"),
> device_name);
> - ext2fs_close (fs);
> + fprintf(stderr,
> + _("Please run 'e2fsck -fy %s' to fix the filesystem\n"
> + "after the aborted resize operation"), device_name);
> + fs->super->s_state |= EXT2_ERROR_FS;
> + ext2fs_mark_super_dirty(fs);
> + ext2fs_close(fs);
> exit(1);
> }
> printf(_("The filesystem on %s is now %u blocks long.\n\n"),
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
