From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bob Peterson <rpeterso@redhat.com>
Date: Tue, 17 Feb 2015 14:09:50 -0500 (EST)
Subject: [Cluster-devel] [GFS2 PATCH] GFS2: Allocate reservation during
 write_begin if needed
In-Reply-To: <54E38FC9.2020709@redhat.com>
References: <1649964129.14531060.1424192978271.JavaMail.zimbra@redhat.com>
	<54E38FC9.2020709@redhat.com>
Message-ID: <2063966524.14688631.1424200190610.JavaMail.zimbra@redhat.com>
List-Id: <cluster-devel.redhat.com>
To: cluster-devel.redhat.com
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

----- Original Message -----
> Hi,
> 
> 
> Since we set the allocation structure when the write call begins, and it
> is not deallocated until there are no writers left with the file open,
> how does this happen?
> 
> Steve.

Hi,

In a normal write, the code goes through gfs2_page_mkwrite or
gfs2_file_aio_write. In the failing scenario, it's going through
sendfile. I suppose I could patch sendfile as an alternative, but
the advantage here is that this patch will do it only if a block
allocation is needed.

Regards,

Bob Peterson
Red Hat File Systems