From: David Sterba <dsterba@suse.cz>
To: Wang Xiaoguang <wangxg.fnst@cn.fujitsu.com>
Cc: linux-btrfs@vger.kernel.org, jbacik@fb.com, dsterba@suse.com,
s.priebe@profihost.ag
Subject: Re: [PATCH 2/2] btrfs: fix false enospc for compression
Date: Mon, 17 Oct 2016 17:05:23 +0200 [thread overview]
Message-ID: <20161017150523.GM11398@twin.jikos.cz> (raw)
In-Reply-To: <57FDAA2A.5040505@cn.fujitsu.com>
On Wed, Oct 12, 2016 at 11:12:42AM +0800, Wang Xiaoguang wrote:
> hi,
>
> Stefan often reports enospc error in his servers when having btrfs
> compression
> enabled. Now he has applied these 2 patches to run and no enospc error
> occurs
> for more than 6 days, it seems they are useful :)
>
> And these 2 patches are somewhat big, please check it, thanks.
It is. As per testing results from Stefan and Holger, I'll add them to
for-next, but won't queue them for merging until they get Josef's
blessing.
next prev parent reply other threads:[~2016-10-17 15:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-06 2:51 [PATCH 1/2] btrfs: improve inode's outstanding_extents computation Wang Xiaoguang
2016-10-06 2:51 ` [PATCH 2/2] btrfs: fix false enospc for compression Wang Xiaoguang
2016-10-06 3:51 ` Wang Xiaoguang
2016-10-12 3:12 ` Wang Xiaoguang
2016-10-17 15:05 ` David Sterba [this message]
2016-10-14 13:09 ` Stefan Priebe - Profihost AG
2016-10-14 13:59 ` Holger Hoffstätte
2016-10-17 9:01 ` Wang Xiaoguang
2016-10-19 14:23 ` David Sterba
2016-10-25 10:43 ` Wang Xiaoguang
2016-10-14 13:09 ` [PATCH 1/2] btrfs: improve inode's outstanding_extents computation Stefan Priebe - Profihost AG
2016-10-23 17:45 ` Stefan Priebe - Profihost AG
2016-11-01 10:18 Wang Xiaoguang
2016-11-01 10:18 ` [PATCH 2/2] btrfs: fix false enospc for compression Wang Xiaoguang
2016-11-01 10:28 ` Wang Xiaoguang
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=20161017150523.GM11398@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=dsterba@suse.com \
--cc=jbacik@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=s.priebe@profihost.ag \
--cc=wangxg.fnst@cn.fujitsu.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 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.