linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Behrens <sbehrens@giantdisaster.de>
To: Josef Bacik <jbacik@fusionio.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs: create the uuid tree on remount rw
Date: Sat, 21 Sep 2013 09:11:38 +0200	[thread overview]
Message-ID: <523D46AA.8060408@giantdisaster.de> (raw)
In-Reply-To: <20130921023320.GD5672@localhost.localdomain>

On 09/21/2013 04:33, Josef Bacik wrote:
> Users have been complaining of the uuid tree stuff warning that there is no uuid
> root when trying to do snapshot operations.  This is because if you mount -o ro
> we will not create the uuid tree.  But then if you mount -o rw,remount we will
> still not create it and then any subsequent snapshot/subvol operations you try
> to do will fail gloriously.  Fix this by creating the uuid_root on remount rw if
> it was not already there.  Thanks,
>
> Signed-off-by: Josef Bacik <jbacik@fusionio.com>
> ---
>   fs/btrfs/super.c | 10 ++++++++++
>   1 file changed, 10 insertions(+)
>
> diff --git a/fs/btrfs/super.c b/fs/btrfs/super.c
> index 6ab0df5..05cfd79 100644
> --- a/fs/btrfs/super.c
> +++ b/fs/btrfs/super.c
> @@ -1383,6 +1383,16 @@ static int btrfs_remount(struct super_block *sb, int *flags, char *data)
>   			pr_warn("btrfs: failed to resume dev_replace\n");
>   			goto restore;
>   		}
> +
> +		if (!fs_info->uuid_root) {
> +			pr_info("btrfs: creating UUID tree\n");
> +			ret = btrfs_create_uuid_tree(fs_info);
> +			if (ret) {
> +				pr_warn("btrfs: failed to create the uuid "
> +					"%d\n", ret);

pr_warn("btrfs: failed to create the uuid tree "
                                           ^^^^

And I'm just wondering what would happen if you remount -o ro,remount 
(or umount -rf or shutdown on a busy filesystem which also causes a ro 
remount) while the uuid tree create/check thread is running. There is no 
code to stop the thread. There is only code for the regulat umount case 
that waits for this thread to complete. But that's not related to your 
patch. I'll put it on my todo list.


> +				goto restore;
> +			}
> +		}
>   		sb->s_flags &= ~MS_RDONLY;
>   	}
>   out:
>



      reply	other threads:[~2013-09-21  7:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-21  2:33 [PATCH] Btrfs: create the uuid tree on remount rw Josef Bacik
2013-09-21  7:11 ` Stefan Behrens [this message]

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=523D46AA.8060408@giantdisaster.de \
    --to=sbehrens@giantdisaster.de \
    --cc=jbacik@fusionio.com \
    --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).