Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Anand Jain <Anand.Jain@oracle.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>,
	Alexander Block <ablock84@googlemail.com>
Subject: Re: [PATCH 2/2 V2] btrfs-progs: update generation_v2 in btrfs_update_root
Date: Mon, 22 Apr 2013 17:31:15 +0800	[thread overview]
Message-ID: <51750363.5020604@oracle.com> (raw)
In-Reply-To: <5174C7B9.8000802@redhat.com>


>   	/*
> -	* If the btrfs-progs is newer and kernel is at
> -	* generation_v1 then we don't touch v2 items
> -	* otherwise when kernel is at same or greater
> -	* version compared with btrfs-progs then update
> -	* the needed
> -	*/
> -	old_size = btrfs_item_size_nr(l, slot);
> -	if (old_size >= sizeof(*item)) {
> -		btrfs_set_root_generation_v2(item,
> -			btrfs_root_generation(item));
> +	 * If this is the first time we update the root item which originated
> +	 * from an older kernel, we need to enlarge the item size to make room
> +	 * for the added fields.
> +	 */
> +	if (old_len < sizeof(*item)) {

  With this fix. when kernel is using v1 and btrfs-progs is
  using v2, the disk structure will be changed to v2 after
  running btrfs check. I would rather take a conservative
  approach, by maintaining kernel intended version.

  Thanks, Anand

  reply	other threads:[~2013-04-22  9:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-22  5:01 [PATCH 1/2] btrfs-progs: set generation_v2 any time we write a new root Eric Sandeen
2013-04-22  5:13 ` [PATCH 2/2] btrfs-progs: enlarge root item if needed in btrfs_update_root Eric Sandeen
2013-04-22  5:16   ` [PATCH 2/2 V2] btrfs-progs: update generation_v2 " Eric Sandeen
2013-04-22  9:31     ` Anand Jain [this message]
2013-04-22 14:01       ` Eric Sandeen
2013-04-23 16:47     ` David Sterba
2013-04-22  9:30 ` [PATCH 1/2] btrfs-progs: set generation_v2 any time we write a new root Anand Jain

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=51750363.5020604@oracle.com \
    --to=anand.jain@oracle.com \
    --cc=ablock84@googlemail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=sandeen@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox