From: Lachlan McIlroy <lachlan@sgi.com>
To: Lachlan McIlroy <lachlan@sgi.com>, xfs-dev <xfs-dev@sgi.com>,
xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH] Increase the default size of the reserved blocks pool
Date: Tue, 30 Sep 2008 16:19:56 +1000 [thread overview]
Message-ID: <48E1C50C.20604@sgi.com> (raw)
In-Reply-To: <20080930041149.GA23915@disturbed>
Dave Chinner wrote:
> On Mon, Sep 29, 2008 at 06:54:13PM +1000, Lachlan McIlroy wrote:
>> The current default size of the reserved blocks pool is easy to deplete
>> with certain workloads, in particular workloads that do lots of concurrent
>> delayed allocation extent conversions. If enough transactions are running
>> in parallel and the entire pool is consumed then subsequent calls to
>> xfs_trans_reserve() will fail with ENOSPC. Also add a rate limited
>> warning so we know if this starts happening again.
>>
>> --- a/fs/xfs/xfs_mount.c 2008-09-29 18:30:26.000000000 +1000
>> +++ b/fs/xfs/xfs_mount.c 2008-09-29 18:27:37.000000000 +1000
>> @@ -1194,7 +1194,7 @@ xfs_mountfs(
>> */
>> resblks = mp->m_sb.sb_dblocks;
>> do_div(resblks, 20);
>> - resblks = min_t(__uint64_t, resblks, 1024);
>> + resblks = min_t(__uint64_t, resblks, 16384);
>
> I'm still not convinced such a large increase is needed for average
> case. This means that at a filesystem size of 5GB we are reserving
> 256MB (5%) for a corner case workload that is unlikely to be run on a
> 5GB filesystem. That is a substantial reduction in space for such
> a filesystem, and quite possibly will drive systems into immediate
> ENOSPC at mount. At that point stuff is going to fail badly during
> boot.
What the? Just last week you were trying to convince me that increasing
the pool size was a good idea.
>
> Indeed - this will ENOSPC the root drive on my laptop the moment I
> apply it (6GB root, 200MB free) and reboot, as well as my main
> server (4GB root - 150MB free, 2GB /var - 100MB free, etc).
> On that basis alone, I'd suggest this is a bad change to make to the
> default value of the reserved block pool.
>
>> error = xfs_reserve_blocks(mp, &resblks, NULL);
>> if (error)
>> cmn_err(CE_WARN, "XFS: Unable to allocate reserve blocks. "
>> @@ -1483,6 +1483,7 @@ xfs_mod_incore_sb_unlocked(
>> int scounter; /* short counter for 32 bit fields */
>> long long lcounter; /* long counter for 64 bit fields */
>> long long res_used, rem;
>> + static int depleted = 0;
>>
>> /*
>> * With the in-core superblock spin lock held, switch
>> @@ -1535,6 +1536,9 @@ xfs_mod_incore_sb_unlocked(
>> if (rsvd) {
>> lcounter = (long long)mp->m_resblks_avail + delta;
>> if (lcounter < 0) {
>> + if ((depleted % 100) == 0)
>> + printk(KERN_DEBUG "XFS reserved blocks pool depleted.\n");
>> + depleted++;
>> return XFS_ERROR(ENOSPC);
>> }
>
> This should use the generic printk ratelimiter, and the error message
> should use xfs_fs_cmn_err() to indicate what filesystem the error
> is occuring on. ie.:
>
> if (printk_ratelimit())
> xfs_fs_cmn_err(CE_WARN, mp,
> "ENOSPC: reserved block pool empty");
Okay, I didn't know about printk_ratelimit(). Hmmm, that routine is not
entirely useful - if the system is generating lots of log messages then
it could suppress the one key message that indicates what's really going
on.
next prev parent reply other threads:[~2008-09-30 6:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-29 8:54 [PATCH] Increase the default size of the reserved blocks pool Lachlan McIlroy
2008-09-30 3:26 ` Mark Goodwin
2008-09-30 4:25 ` Dave Chinner
2008-09-30 6:08 ` Lachlan McIlroy
2008-09-30 6:37 ` Dave Chinner
2008-09-30 4:11 ` Dave Chinner
2008-09-30 4:29 ` Dave Chinner
2008-09-30 6:19 ` Lachlan McIlroy [this message]
2008-09-30 6:40 ` Dave Chinner
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=48E1C50C.20604@sgi.com \
--to=lachlan@sgi.com \
--cc=xfs-dev@sgi.com \
--cc=xfs@oss.sgi.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