All of lore.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: Omar Sandoval <osandov@osandov.com>,
	<linux-btrfs@vger.kernel.org>, David Sterba <dsterba@suse.com>
Cc: <kernel-team@fb.com>
Subject: Re: [PATCH v2] btrfs-progs: report I/O errors when closing the filesystem
Date: Mon, 6 Mar 2017 08:42:01 +0800	[thread overview]
Message-ID: <ab252cb5-b59e-d445-b69c-0dfe15c0861a@cn.fujitsu.com> (raw)
In-Reply-To: <105e3aa192a47f3936c2ac47ad8d673745cccaea.1488560489.git.osandov@fb.com>



At 03/04/2017 01:02 AM, Omar Sandoval wrote:
> From: Omar Sandoval <osandov@fb.com>
>
> If the final fsync() on the Btrfs device fails, we just swallow the
> error and don't alert the user in any way. This was uncovered by xfstest
> generic/405, which checks that mkfs fails when it encounters EIO.
>
> Signed-off-by: Omar Sandoval <osandov@fb.com>

Please ignore my comment on v1 patch, didn't see the v2 one.

Looks good to me.

Reviewed-by: Qu Wenruo <quwenruo@cn.fujitsu.com>

Thanks,
Qu
> ---
> Changes from v1: return -errno instead of -1
>
>  disk-io.c | 4 ++--
>  volumes.c | 9 +++++++--
>  2 files changed, 9 insertions(+), 4 deletions(-)
>
> diff --git a/disk-io.c b/disk-io.c
> index 2a94d4fc..48fb3c6b 100644
> --- a/disk-io.c
> +++ b/disk-io.c
> @@ -1817,10 +1817,10 @@ int close_ctree_fs_info(struct btrfs_fs_info *fs_info)
>  	free_fs_roots_tree(&fs_info->fs_root_tree);
>
>  	btrfs_release_all_roots(fs_info);
> -	btrfs_close_devices(fs_info->fs_devices);
> +	ret = btrfs_close_devices(fs_info->fs_devices);
>  	btrfs_cleanup_all_caches(fs_info);
>  	btrfs_free_fs_info(fs_info);
> -	return 0;
> +	return ret;
>  }
>
>  int clean_tree_block(struct btrfs_trans_handle *trans, struct btrfs_root *root,
> diff --git a/volumes.c b/volumes.c
> index a0a85edd..f7d82d51 100644
> --- a/volumes.c
> +++ b/volumes.c
> @@ -160,6 +160,7 @@ int btrfs_close_devices(struct btrfs_fs_devices *fs_devices)
>  {
>  	struct btrfs_fs_devices *seed_devices;
>  	struct btrfs_device *device;
> +	int ret = 0;
>
>  again:
>  	if (!fs_devices)
> @@ -168,7 +169,11 @@ again:
>  		device = list_entry(fs_devices->devices.next,
>  				    struct btrfs_device, dev_list);
>  		if (device->fd != -1) {
> -			fsync(device->fd);
> +			if (fsync(device->fd) == -1) {
> +				warning("fsync on device %llu failed: %s",
> +					device->devid, strerror(errno));
> +				ret = -errno;
> +			}
>  			if (posix_fadvise(device->fd, 0, 0, POSIX_FADV_DONTNEED))
>  				fprintf(stderr, "Warning, could not drop caches\n");
>  			close(device->fd);
> @@ -197,7 +202,7 @@ again:
>  		free(fs_devices);
>  	}
>
> -	return 0;
> +	return ret;
>  }
>
>  void btrfs_close_all_devices(void)
>



  reply	other threads:[~2017-03-06  0:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-03 16:59 [PATCH] btrfs-progs: report I/O errors when closing the filesystem Omar Sandoval
2017-03-03 17:02 ` [PATCH v2] " Omar Sandoval
2017-03-06  0:42   ` Qu Wenruo [this message]
2017-03-08 12:18     ` David Sterba
2017-03-06  0:40 ` [PATCH] " Qu Wenruo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ab252cb5-b59e-d445-b69c-0dfe15c0861a@cn.fujitsu.com \
    --to=quwenruo@cn.fujitsu.com \
    --cc=dsterba@suse.com \
    --cc=kernel-team@fb.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=osandov@osandov.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.