From: Dave Chinner <david@fromorbit.com>
To: Avi Kivity <avi@scylladb.com>
Cc: Brian Foster <bfoster@redhat.com>, linux-xfs@vger.kernel.org
Subject: Re: xfs_extent_busy_flush vs. aio
Date: Thu, 8 Feb 2018 10:43:51 +1100 [thread overview]
Message-ID: <20180207234350.GA20266@dastard> (raw)
In-Reply-To: <9184712f-65e8-5591-2f2f-aeba48cde3f4@scylladb.com>
On Wed, Feb 07, 2018 at 12:54:43PM +0200, Avi Kivity wrote:
> On 02/07/2018 03:57 AM, Dave Chinner wrote:
> >IOWs, inode32 limits where and how many inodes you can
> >create, not how much user data you can write inode the filesystem.
>
> Thanks a lot for the clarifications. Looks like inode32 can be used
> to reduce some of our pain.
>
> There's a danger that when switching from inode64 to inode32 you end
> up with the inode32 address space already exhausted, right? Does
> that result in ENOSPC or what?
ENOSPC on inode allocation.
> Anyway, can probably be fixed by stopping the load, copying files
> around, and moving them back.
Yup, assuming you're able to find the files that need to be moved in
a finite period of time.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2018-02-07 23:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-23 14:57 xfs_extent_busy_flush vs. aio Avi Kivity
2018-01-23 15:28 ` Brian Foster
2018-01-23 15:45 ` Avi Kivity
2018-01-23 16:11 ` Brian Foster
2018-01-23 16:22 ` Avi Kivity
2018-01-23 16:47 ` Brian Foster
2018-01-23 17:00 ` Avi Kivity
2018-01-23 17:39 ` Brian Foster
2018-01-25 8:50 ` Avi Kivity
2018-01-25 13:08 ` Brian Foster
2018-01-29 9:40 ` Avi Kivity
2018-01-29 11:35 ` Dave Chinner
2018-01-29 11:44 ` Avi Kivity
2018-01-29 21:56 ` Dave Chinner
2018-01-30 8:58 ` Avi Kivity
2018-02-06 14:10 ` Avi Kivity
2018-02-07 1:57 ` Dave Chinner
2018-02-07 10:54 ` Avi Kivity
2018-02-07 23:43 ` Dave Chinner [this message]
2018-02-02 9:48 ` Christoph Hellwig
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=20180207234350.GA20266@dastard \
--to=david@fromorbit.com \
--cc=avi@scylladb.com \
--cc=bfoster@redhat.com \
--cc=linux-xfs@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.