linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miklos Szeredi <miklos@szeredi.hu>
To: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	fuse-devel <fuse-devel@lists.sourceforge.net>,
	Maxim Patlasov <mpatlasov@parallels.com>,
	Miklos Szeredi <mszeredi@redhat.com>
Subject: Re: [fuse] How to trigger writeback?
Date: Mon, 24 Sep 2018 10:15:03 +0200	[thread overview]
Message-ID: <CAJfpegse5hntdfHMOjr8k2Ltw8Jdg_afaZV7fsghbpNt0VgGHw@mail.gmail.com> (raw)
In-Reply-To: <87zhw7s4qb.fsf@thinkpad.rath.org>

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).

I'm working on new interfaces that will allow, among other things,
triggering sync from the server.

> Background: I am emulating the reflink ioctl with a magic xattr, but for
> that to work the filesystem needs to have all the data that is supposed
> to be in the copied file.

Have a look at the copyfile patch on the for-next branch of

  git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git

Adding reflink support based on that should be pretty simple (and it
takes care of flushing dirty pages).

Thanks,
Miklos

  reply	other threads:[~2018-09-24 14:15 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 [this message]
2018-09-25  8:30   ` [fuse-devel] " Nikolaus Rath
2018-09-25  8:48     ` Miklos Szeredi
2018-09-27  8:28       ` Nikolaus Rath

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=CAJfpegse5hntdfHMOjr8k2Ltw8Jdg_afaZV7fsghbpNt0VgGHw@mail.gmail.com \
    --to=miklos@szeredi.hu \
    --cc=fuse-devel@lists.sourceforge.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=mpatlasov@parallels.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).