From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] gfs2: Special-case rindex for gfs2_grow
Date: Wed, 25 Jul 2018 15:05:36 -0400 (EDT) [thread overview]
Message-ID: <990954492.54306840.1532545536791.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20180725185955.8207-1-agruenba@redhat.com>
----- Original Message -----
> To speed up the common case of appending to a file,
> gfs2_write_alloc_required presumes that writing beyond the end of a file
> will always require additional blocks to be allocated. This assumption
> is incorrect for preallocates files, but there are no negative
> consequences as long as *some* space is still left on the filesystem.
>
> One special file that always has some space preallocated beyond the end
> of the file is the rindex: when growing a filesystem, gfs2_grow adds one
> or more new resource groups and appends records describing those
> resource groups to the rindex; the preallocated space ensures that this
> is always possible.
>
> However, when a filesystem is completely full, gfs2_write_alloc_required
> will indicate that an additional allocation is required, and appending
> the next record to the rindex will fail even though space for that
> record has already been preallocated. To fix that, skip the incorrect
> optimization in gfs2_write_alloc_required, but for the rindex only.
> Other writes to preallocated space beyond the end of the file are still
> allowed to fail on completely full filesystems.
>
> Signed-off-by: Andreas Gruenbacher <agruenba@redhat.com>
Hi,
ACK. Yeah, we need this.
Bob Peterson
prev parent reply other threads:[~2018-07-25 19:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-25 18:59 [Cluster-devel] [PATCH] gfs2: Special-case rindex for gfs2_grow Andreas Gruenbacher
2018-07-25 19:05 ` Bob Peterson [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=990954492.54306840.1532545536791.JavaMail.zimbra@redhat.com \
--to=rpeterso@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).