-------- Original Message --------
Subject: Re: [RFC PATCH 0/2] Kernel space btrfs missing device detection.
From: Goffredo Baroncelli <kreij...@libero.it>
To: Qu Wenruo <quwen...@cn.fujitsu.com>, linux-btrfs@vger.kernel.org
Date: 2014年05月07日 02:10
Hi,

instead of extending the BTRFS_IOCTL_DEV_INFO ioctl, why do not add a field under 
/sys/fs/btrfs/<UUID>/ ? Something like /sys/fs/btrfs/<UUID>/missing_device

BR
G.Baroncelli
I think that is also a good idea. I'll try to add it later.

Thanks
Qu


On 05/06/2014 08:33 AM, Qu Wenruo wrote:
Original btrfs will not detection any missing device since there is
no notification mechanism for fs layer to detect missing device in
block layer.

However we don't really need to notify fs layer upon dev remove,
probing in dev_info/rm_dev ioctl is good enough since they are the
only two ioctls caring about missing device.

This patchset will do ioctl time missing dev detection and return
device missing status in dev_info ioctl using a new member in
btrfs_ioctl_dev_info_args with a backward compatible method.

Cc: Anand Jain <anand.j...@oracle.com> Qu Wenruo (2): btrfs: Add
missing device check in dev_info/rm_dev ioctl btrfs: Add new member
of btrfs_ioctl_dev_info_args.

fs/btrfs/ioctl.c           |  4 ++++ fs/btrfs/volumes.c         | 25
++++++++++++++++++++++++- fs/btrfs/volumes.h         |  2 ++
include/uapi/linux/btrfs.h |  5 ++++- 4 files changed, 34
insertions(+), 2 deletions(-)



--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to