From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-it1-f195.google.com ([209.85.166.195]:39617 "EHLO mail-it1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726208AbeIYOzH (ORCPT ); Tue, 25 Sep 2018 10:55:07 -0400 Received: by mail-it1-f195.google.com with SMTP id w200-v6so5996140itc.4 for ; Tue, 25 Sep 2018 01:48:39 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <8736tyrncj.fsf@thinkpad.rath.org> References: <87zhw7s4qb.fsf@thinkpad.rath.org> <8736tyrncj.fsf@thinkpad.rath.org> From: Miklos Szeredi Date: Tue, 25 Sep 2018 10:48:37 +0200 Message-ID: Subject: Re: [fuse-devel] [fuse] How to trigger writeback? To: fuse-devel , Miklos Szeredi , linux-fsdevel Content-Type: text/plain; charset="UTF-8" Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Tue, Sep 25, 2018 at 10:30 AM, Nikolaus Rath wrote: > On Sep 24 2018, Miklos Szeredi wrote: >> On Mon, Sep 24, 2018 at 10:02 AM, Nikolaus Rath wrote: >>> Hi, >>> >>> How do I trigger writeback from a (writeback-cache enabled) FUSE >>> filesystem? >> >> No way, currently (well, triggering fsync(2)/fdatasync(2) on the >> filesystem would work, but such recursion is considered highly >> hackish). > > > You mean sync(2)/syncfs(2), not fsync(), right? Unless my manpages are > out of date, fsync() only works on a specific inode. I would've thought you only need writeback of a specific inode for reflink, no? Thanks, Miklos