linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Goffredo Baroncelli <kreijack@libero.it>
To: Josef Bacik <jbacik@fusionio.com>
Cc: linux-btrfs@vger.kernel.org, harald@redhat.com
Subject: Re: [PATCH] Btrfs: add DEVICE_READY ioctl
Date: Fri, 22 Jun 2012 20:12:52 +0200	[thread overview]
Message-ID: <4FE4B5A4.90603@libero.it> (raw)
In-Reply-To: <1340309431-9972-2-git-send-email-jbacik@fusionio.com>

On 06/21/2012 10:10 PM, Josef Bacik wrote:
> This will be used in conjunction with btrfs device ready <dev>.  This is
> needed for initrd's to have a nice and lightweight way to tell if all of the
> devices needed for a file system are in the cache currently.  This keeps
> them from having to do mount+sleep loops waiting for devices to show up.
> Thanks,
> 
> Signed-off-by: Josef Bacik <jbacik@fusionio.com>
> ---
>  fs/btrfs/ioctl.h   |    3 ++-
>  fs/btrfs/super.c   |    7 +++++++
>  fs/btrfs/volumes.c |    9 ++++++++-
>  fs/btrfs/volumes.h |    1 +
>  4 files changed, 18 insertions(+), 2 deletions(-)
> 
> diff --git a/fs/btrfs/ioctl.h b/fs/btrfs/ioctl.h
> index 497c530..34317cf 100644
> --- a/fs/btrfs/ioctl.h
> +++ b/fs/btrfs/ioctl.h
> @@ -363,5 +363,6 @@ struct btrfs_ioctl_get_dev_stats {
>  				      struct btrfs_ioctl_get_dev_stats)
>  #define BTRFS_IOC_GET_AND_RESET_DEV_STATS _IOWR(BTRFS_IOCTL_MAGIC, 53, \
>  					struct btrfs_ioctl_get_dev_stats)
> -
> +#define BTRFS_IOC_DEVICES_READY _IOW(BTRFS_IOCTL_MAGIC, 54, \
> +				     struct btrfs_ioctl_vol_args)

What is the purpose of the ioctl args ? This could confuses the user (as
programmer). However IIRC for the other ioctls without argument the same
policy was applied.Maybe a better name than btrfs_ioctl_vol_args would
help, like btrfs_generic_ioctl.

Anyway, I suggest to return not a boolean value but a pair of integers:
both the number of devices registered and the total number of devices.
Better would be the dev-id found and the dev-id missing. This could help
a lot the diagnostic of mount problem.

Finally I am starting to think that we should definitely switch to a
/sys/btrfs style of interface

think something like:

/sys/btrfs/<fs-uuid>/<dev-uuid>/present
                               size
                               space-occuped
                               number-of-error
                               [...]

/sys/btrfs/<fs-uuid>/<subvolume-id>/read-only
                                    compressed
                                    raid-mode
                                    path
                                    [...]

/sys/btrfs/<fs-uuid>/label
                     mounted
                     read-only
                     compressed
                     raid-mode
                     [...]


>  #endif
> diff --git a/fs/btrfs/super.c b/fs/btrfs/super.c
> index 23fc7e8..347ccd8 100644
> --- a/fs/btrfs/super.c
> +++ b/fs/btrfs/super.c
> @@ -1458,6 +1458,13 @@ static long btrfs_control_ioctl(struct file *file, unsigned int cmd,
>  		ret = btrfs_scan_one_device(vol->name, FMODE_READ,
>  					    &btrfs_fs_type, &fs_devices);
>  		break;
> +	case BTRFS_IOC_DEVICES_READY:
> +		ret = btrfs_scan_one_device(vol->name, FMODE_READ,
> +					    &btrfs_fs_type, &fs_devices);
> +		if (ret)
> +			break;
> +		ret = !(fs_devices->num_devices == fs_devices->total_devices);
> +		break;
>  	}
>  
>  	kfree(vol);
> diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
> index 3f292cf..a505627 100644
> --- a/fs/btrfs/volumes.c
> +++ b/fs/btrfs/volumes.c
> @@ -429,6 +429,7 @@ static struct btrfs_fs_devices *clone_fs_devices(struct btrfs_fs_devices *orig)
>  	mutex_init(&fs_devices->device_list_mutex);
>  	fs_devices->latest_devid = orig->latest_devid;
>  	fs_devices->latest_trans = orig->latest_trans;
> +	fs_devices->total_devices = orig->total_devices;
>  	memcpy(fs_devices->fsid, orig->fsid, sizeof(fs_devices->fsid));
>  
>  	/* We have held the volume lock, it is safe to get the devices. */
> @@ -739,6 +740,7 @@ int btrfs_scan_one_device(const char *path, fmode_t flags, void *holder,
>  	int ret;
>  	u64 devid;
>  	u64 transid;
> +	u64 total_devices;
>  
>  	flags |= FMODE_EXCL;
>  	bdev = blkdev_get_by_path(path, flags, holder);
> @@ -760,6 +762,7 @@ int btrfs_scan_one_device(const char *path, fmode_t flags, void *holder,
>  	disk_super = (struct btrfs_super_block *)bh->b_data;
>  	devid = btrfs_stack_device_id(&disk_super->dev_item);
>  	transid = btrfs_super_generation(disk_super);
> +	total_devices = btrfs_super_num_devices(disk_super);
>  	if (disk_super->label[0])
>  		printk(KERN_INFO "device label %s ", disk_super->label);
>  	else
> @@ -767,7 +770,8 @@ int btrfs_scan_one_device(const char *path, fmode_t flags, void *holder,
>  	printk(KERN_CONT "devid %llu transid %llu %s\n",
>  	       (unsigned long long)devid, (unsigned long long)transid, path);
>  	ret = device_list_add(path, disk_super, devid, fs_devices_ret);
> -
> +	if (!ret && fs_devices_ret)
> +		(*fs_devices_ret)->total_devices = total_devices;
>  	brelse(bh);
>  error_close:
>  	mutex_unlock(&uuid_mutex);
> @@ -1433,6 +1437,7 @@ int btrfs_rm_device(struct btrfs_root *root, char *device_path)
>  	list_del_rcu(&device->dev_list);
>  
>  	device->fs_devices->num_devices--;
> +	device->fs_devices->total_devices--;
>  
>  	if (device->missing)
>  		root->fs_info->fs_devices->missing_devices--;
> @@ -1550,6 +1555,7 @@ static int btrfs_prepare_sprout(struct btrfs_root *root)
>  	fs_devices->seeding = 0;
>  	fs_devices->num_devices = 0;
>  	fs_devices->open_devices = 0;
> +	fs_devices->total_devices = 0;
>  	fs_devices->seed = seed_devices;
>  
>  	generate_random_uuid(fs_devices->fsid);
> @@ -1749,6 +1755,7 @@ int btrfs_init_new_device(struct btrfs_root *root, char *device_path)
>  	root->fs_info->fs_devices->num_devices++;
>  	root->fs_info->fs_devices->open_devices++;
>  	root->fs_info->fs_devices->rw_devices++;
> +	root->fs_info->fs_devices->total_devices++;
>  	if (device->can_discard)
>  		root->fs_info->fs_devices->num_can_discard++;
>  	root->fs_info->fs_devices->total_rw_bytes += device->total_bytes;
> diff --git a/fs/btrfs/volumes.h b/fs/btrfs/volumes.h
> index 74366f2..a3c5d5c 100644
> --- a/fs/btrfs/volumes.h
> +++ b/fs/btrfs/volumes.h
> @@ -126,6 +126,7 @@ struct btrfs_fs_devices {
>  	u64 missing_devices;
>  	u64 total_rw_bytes;
>  	u64 num_can_discard;
> +	u64 total_devices;
>  	struct block_device *latest_bdev;
>  
>  	/* all of the devices in the FS, protected by a mutex


  reply	other threads:[~2012-06-22 18:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-21 20:10 [RFC] A way to tell if all the devices in a file system are available Josef Bacik
2012-06-21 20:10 ` [PATCH] Btrfs: add DEVICE_READY ioctl Josef Bacik
2012-06-22 18:12   ` Goffredo Baroncelli [this message]
2012-07-17 11:53     ` David Sterba
2012-07-17 17:17       ` Goffredo Baroncelli
2012-06-21 20:10 ` [PATCH] Btrfs-progs: add btrfs device ready command Josef Bacik
2012-06-22 17:20   ` Goffredo Baroncelli
2012-06-22 10:33 ` [RFC] A way to tell if all the devices in a file system are available Harald Hoyer
2012-07-10 17:35 ` Harald Hoyer

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=4FE4B5A4.90603@libero.it \
    --to=kreijack@libero.it \
    --cc=harald@redhat.com \
    --cc=jbacik@fusionio.com \
    --cc=kreijack@inwind.it \
    --cc=linux-btrfs@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).