From: Robert Mustacchi <rm@fingolfin.org>
To: illumos-developer <developer@lists.illumos.org>,
Gordon Ross <gordon.w.ross@gmail.com>
Subject: Re: [developer] 16675 want syncfs(3C)
Date: Sun, 28 Jul 2024 11:10:28 -0700 [thread overview]
Message-ID: <c2746d14-8d03-4ef1-9f82-3c7ae6813184@fingolfin.org> (raw)
In-Reply-To: <CAD0Ztp38nOt4=6GUrm2am7AfAE7E2UL_s2hTbYqeaLhMS66qoQ@mail.gmail.com>
On 7/26/24 18:33, Gordon Ross wrote:
> I read through your write-up in the issue.
> Have you surveyed which file system types on Linux support syncfs(2)?
> I'm curious what they might have done for NFS and SMB, which don't
> really offer a natural way to sync everything under a mount point.
I didn't survey it too extensively. The structure of the VFS between the
systems is a bit different. In our case the VFS_SYNC and VFS_SYNCFS
entry point expects the file system to determine dirty vnodes, schedule
writes, and related. While not all file systems implement the specific
sync_fs() entry point, other logic is called around there that does
something for all file systems, the specifics I couldn't say. NFS and
SMB don't implement the sync_fs() file system specific vector over there.
Robert
> On Thu, Jul 25, 2024 at 8:09 PM Robert Mustacchi <rm@fingolfin.org> wrote:
>>
>> On 7/25/24 17:03, Richard Lowe wrote:
>>> I think this was meant to be https://code.illumos.org/c/illumos-gate/+/3609
>>
>> Oops, it was. Thanks for catching that.
>>
>> Robert
>>
>
> ------------------------------------------
> illumos: illumos-developer
> Permalink: https://illumos.topicbox.com/groups/developer/T1f0f6493c10b2c62-M9aa42cc3f2af94588b816c9c
> Delivery options: https://illumos.topicbox.com/groups/developer/subscription
prev parent reply other threads:[~2024-07-28 18:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-25 22:59 Robert Mustacchi
2024-07-26 0:03 ` [developer] " Richard Lowe
2024-07-26 0:09 ` Robert Mustacchi
2024-07-27 1:33 ` Gordon Ross
2024-07-28 18:10 ` Robert Mustacchi [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=c2746d14-8d03-4ef1-9f82-3c7ae6813184@fingolfin.org \
--to=rm@fingolfin.org \
--cc=developer@lists.illumos.org \
--cc=gordon.w.ross@gmail.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).