From: Nikolaus Rath <Nikolaus@rath.org>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: fuse-devel <fuse-devel@lists.sourceforge.net>,
Miklos Szeredi <mszeredi@redhat.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [fuse-devel] [fuse] How to trigger writeback?
Date: Thu, 27 Sep 2018 09:28:29 +0100 [thread overview]
Message-ID: <87zhw3qr82.fsf@thinkpad.rath.org> (raw)
In-Reply-To: <CAJfpegvAhW4UUhD+SziLHsagPY=BLyZU0MKOov8z18woywyxDw@mail.gmail.com> (Miklos Szeredi's message of "Tue, 25 Sep 2018 10:48:37 +0200")
On Sep 25 2018, Miklos Szeredi <miklos@szeredi.hu> wrote:
> On Tue, Sep 25, 2018 at 10:30 AM, Nikolaus Rath <Nikolaus@rath.org> wrote:
>> On Sep 24 2018, Miklos Szeredi <miklos@szeredi.hu> wrote:
>>> On Mon, Sep 24, 2018 at 10:02 AM, Nikolaus Rath <Nikolaus@rath.org> 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?
Aeh, yeah, I did not mention that. Since I couldn't implement real
reflink support but have to go through xattrs, my "reflink" also
supports reflinking entire directory trees. I guess I could still issue
a bunch of fsyncs(), but I think syncfs() is nicer (I can even move it
into the client program that sets the magic xattr so that the filesystem
does not call into itself).
Best,
-Nikolaus
--
GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
prev parent reply other threads:[~2018-09-27 14:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-24 8:02 [fuse] How to trigger writeback? Nikolaus Rath
2018-09-24 8:15 ` Miklos Szeredi
2018-09-25 8:30 ` [fuse-devel] " Nikolaus Rath
2018-09-25 8:48 ` Miklos Szeredi
2018-09-27 8:28 ` Nikolaus Rath [this message]
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=87zhw3qr82.fsf@thinkpad.rath.org \
--to=nikolaus@rath.org \
--cc=fuse-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=mszeredi@redhat.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.