cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2 PATCH] GFS2: Reserve journal space for quota change in do_grow
Date: Thu, 27 Jun 2013 18:43:50 +0100	[thread overview]
Message-ID: <1372355030.2774.12.camel@menhir> (raw)
In-Reply-To: <340920540.95675196.1372351671118.JavaMail.root@redhat.com>

Hi,

Thanks - now in the -nmw git tree,

Steve.

On Thu, 2013-06-27 at 12:47 -0400, Bob Peterson wrote:
> Hi,
> 
> If a GFS2 file system is mounted with quotas and a file is grown
> in such a way that its free blocks for the allocation are represented
> in a secondary bitmap, GFS2 ran out of blocks in the transaction.
> That resulted in "fatal: assertion "tr->tr_num_buf <= tr->tr_blocks".
> This patch reserves extra blocks for the quota change so the
> transaction has enough space.
> 
> Regards,
> 
> Bob Peterson
> Red Hat File Systems
> 
> Signed-off-by: Bob Peterson <rpeterso@redhat.com> 
> ---
>  fs/gfs2/bmap.c | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/fs/gfs2/bmap.c b/fs/gfs2/bmap.c
> index 93b5809..5e2f56f 100644
> --- a/fs/gfs2/bmap.c
> +++ b/fs/gfs2/bmap.c
> @@ -1232,7 +1232,9 @@ static int do_grow(struct inode *inode, u64 size)
>  		unstuff = 1;
>  	}
>  
> -	error = gfs2_trans_begin(sdp, RES_DINODE + RES_STATFS + RES_RG_BIT, 0);
> +	error = gfs2_trans_begin(sdp, RES_DINODE + RES_STATFS + RES_RG_BIT +
> +				 (sdp->sd_args.ar_quota == GFS2_QUOTA_OFF ?
> +				  0 : RES_QUOTA), 0);
>  	if (error)
>  		goto do_grow_release;
>  
> 




      reply	other threads:[~2013-06-27 17:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1979146688.95644942.1372351274028.JavaMail.root@redhat.com>
2013-06-27 16:47 ` [Cluster-devel] [GFS2 PATCH] GFS2: Reserve journal space for quota change in do_grow Bob Peterson
2013-06-27 17:43   ` Steven Whitehouse [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=1372355030.2774.12.camel@menhir \
    --to=swhiteho@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;
as well as URLs for NNTP newsgroup(s).