/b6ce39eeb6de8887e66a#file-filefrag-after-fstrim-out
On Wed, Aug 26, 2015 at 11:02 AM, Jun He wrote:
> jun@jun-VirtualBox:~/workdir/b6ce39eeb6de8887e66a$ uname -r
> 4.2.0-rc5-integration-4.3+
>
> https://gist.githubusercontent.com/junhe/b6ce39eeb6de8887e66a/raw/1cd84e6bb138eeb08dc07af2c44dedf998
Thanks for the info. In the attached reproducer, I don't do sync after running
the workload (but I've tried that before.). Just to be sure, I ran again with
sync and waited for 60 seconds before collecting data. The behavior was the
same.
Then I tried one more thing, which corrected btrfs behavio
/26/15 12:04 AM, Jun He wrote:
>> Hi, I have been playing with btrfs discard for a while and found
>> that btrfs may fail to discard some extents with 'mount -o
>> discard'. I am aware of Jeff Mahoney's patches (
>> https://patchwork.kernel.org/patch/6609
Hi,
I have been playing with btrfs discard for a while and found that btrfs may
fail to discard some extents with 'mount -o discard'. I am aware of Jeff
Mahoney's patches ( https://patchwork.kernel.org/patch/6609491/ ). It seems
that the patches do not fix the problem. I have seen the same problema
I just want to let you guys know that there are people
waiting for the final patches of the discard problem :)
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-
