From: Christoph Hellwig <hch@infradead.org>
To: Chris Cottam <chris.cottam@bytemark.co.uk>
Cc: Dave Chinner <david@fromorbit.com>,
Christoph Hellwig <hch@infradead.org>,
"Darrick J. Wong" <darrick.wong@oracle.com>,
linux-xfs@vger.kernel.org
Subject: Re: XFS reflinks
Date: Thu, 31 Aug 2017 06:09:12 -0700 [thread overview]
Message-ID: <20170831130912.GA19544@infradead.org> (raw)
In-Reply-To: <3b025b43-3ca5-567f-d9e0-c45245d37ecb@bytemark.co.uk>
On Thu, Aug 31, 2017 at 11:33:44AM +0100, Chris Cottam wrote:
> > Yup, that's a problem, and it's going to be even more of a problem
> > once people start using reflink to snapshot sparse VM images. I
> > think that the extent rework is probably the most important thing we
> > need to solve for COW to be generally usable.
>
> Assuming I was feeling brave, what should I be doing to limit the
> chances of hitting this issue? Would smaller filesystems or lots of
> memory on the host help etc?
> Also what should I be monitoring to warn me before anything actually breaks?
Make sure you have memory compaction enabled is the best bet,
don't run under crazy memory pressure. I've not actually seen an
actual deadlock due to it, just the possible memory allocation
deadlock warnings from kmem_alloc (and lots of those).
prev parent reply other threads:[~2017-08-31 13:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-29 11:23 XFS reflinks Chris Cottam
2017-08-29 13:00 ` Christoph Hellwig
2017-08-29 13:39 ` Chris Cottam
2017-08-29 16:40 ` Christoph Hellwig
2017-08-29 16:03 ` Darrick J. Wong
2017-08-29 16:23 ` Christoph Hellwig
2017-08-29 22:03 ` Dave Chinner
2017-08-30 7:03 ` Christoph Hellwig
2017-08-31 10:33 ` Chris Cottam
2017-08-31 13:09 ` Christoph Hellwig [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=20170831130912.GA19544@infradead.org \
--to=hch@infradead.org \
--cc=chris.cottam@bytemark.co.uk \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox