From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: bug? fstrim only trims unallocated space, not unused in bg's
Date: Tue, 21 Nov 2017 12:58:05 +0800 [thread overview]
Message-ID: <4b7a0fae-ca96-7583-90d0-37cabc78849b@gmx.com> (raw)
In-Reply-To: <CAJCQCtQiTt78svzzdcV_Pm2iPK6RgYLXsvMda7H6aQeMf2w07g@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 872 bytes --]
On 2017年11月21日 12:49, Chris Murphy wrote:
> On Mon, Nov 20, 2017 at 9:43 PM, Qu Wenruo <quwenruo.btrfs@gmx.com> wrote:
>>
>>
>>>
>>> Apply in addition to previous patch? Or apply to clean v4.14?
>>
>> On previous patch.
>
> Refuses to apply with or without previous patch.
>
> $ git apply -v ~/qufstrim3.patch
> Checking patch fs/btrfs/extent-tree.c...
> error: while searching for:
> int dev_ret = 0;
> int ret = 0;
>
> /*
> * try to trim all FS space, our block group may start from non-zero.
> */
>
> error: patch failed: fs/btrfs/extent-tree.c:10972
> error: fs/btrfs/extent-tree.c: patch does not apply
>
Please try this branch.
It's just previous patch and diff merged together and applied on v4.14
tag from torvalds.
https://github.com/adam900710/linux/tree/tmp
Thanks,
Qu
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 520 bytes --]
next prev parent reply other threads:[~2017-11-21 4:58 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-19 6:17 bug? fstrim only trims unallocated space, not unused in bg's Chris Murphy
2017-11-19 6:27 ` Andrei Borzenkov
2017-11-19 21:38 ` Chris Murphy
[not found] ` <3114a78e-485a-daea-f8b1-48cc330f4209@suse.com>
2017-11-20 20:01 ` Jeff Mahoney
2017-11-20 20:40 ` Jeff Mahoney
2017-11-20 21:56 ` Chris Murphy
2017-11-20 22:59 ` Chris Murphy
2017-11-21 1:46 ` Jeff Mahoney
2017-11-21 4:04 ` Chris Murphy
2017-11-21 4:13 ` Jeff Mahoney
2017-11-21 4:15 ` Chris Murphy
2017-11-20 2:13 ` Qu Wenruo
2017-11-20 2:24 ` Chris Murphy
2017-11-20 2:30 ` Chris Murphy
2017-11-20 2:42 ` Qu Wenruo
2017-11-20 22:23 ` Chris Murphy
2017-11-21 1:16 ` Qu Wenruo
2017-11-21 4:06 ` Chris Murphy
2017-11-21 4:09 ` Chris Murphy
2017-11-21 4:29 ` Qu Wenruo
2017-11-21 4:34 ` Chris Murphy
2017-11-21 4:43 ` Qu Wenruo
2017-11-21 4:46 ` Chris Murphy
2017-11-21 4:49 ` Chris Murphy
2017-11-21 4:58 ` Qu Wenruo [this message]
2017-11-21 5:58 ` Chris Murphy
2017-11-21 6:10 ` Qu Wenruo
2018-04-01 3:28 ` Chris Murphy
2018-04-01 10:34 ` Qu Wenruo
2018-04-01 23:30 ` Chris Murphy
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=4b7a0fae-ca96-7583-90d0-37cabc78849b@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.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