From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from wout2-smtp.messagingengine.com ([64.147.123.25]:37483 "EHLO wout2-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728463AbeIYOgc (ORCPT ); Tue, 25 Sep 2018 10:36:32 -0400 From: Nikolaus Rath To: fuse-devel@lists.sourceforge.net, Miklos Szeredi , linux-fsdevel Subject: Re: [fuse-devel] [fuse] How to trigger writeback? References: <87zhw7s4qb.fsf@thinkpad.rath.org> Date: Tue, 25 Sep 2018 09:30:04 +0100 In-Reply-To: (Miklos Szeredi's message of "Mon, 24 Sep 2018 10:15:03 +0200") Message-ID: <8736tyrncj.fsf@thinkpad.rath.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Sender: linux-fsdevel-owner@vger.kernel.org List-ID: 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. Best, -Nikolaus --=20 GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F =C2=BBTime flies like an arrow, fruit flies like a Banana.=C2= =AB