From: Mike Gilbert <floppym@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] netmount and glusterfs (fuse) dependency management
Date: Thu, 11 Apr 2024 11:53:22 -0400 [thread overview]
Message-ID: <CAJ0EP42P6W5tFVFag912KYyuKHhSfT5jfx_Qsek9wK2nnVXw0Q@mail.gmail.com> (raw)
In-Reply-To: <e9b6b3f4-9943-4eca-877a-bf54c3697caf@uls.co.za>
On Mon, Apr 8, 2024 at 5:51 AM Jaco Kroon <jaco@uls.co.za> wrote:
>
> Hi All,
>
> I was hoping for some advise regarding how I could improve the glusterfs
> package for users (and myself). At least those using openrc, but I
> suspect similar may be applicable to systemd, but I have no idea how
> systemd handles network mounts so perhaps someone could chip in here on
> that front too.
>
> Specifically the mounting of glusterfs file systems currently has a few
> problems (glusterd if server=localhost, network, dns(?) and fuse
> availability). For now the focus is on the fuse aspect since that's the
> biggest annoyance by far.
>
> Mounting happens via the netmount service.
>
> In order for glusterfs to mount successfully the fuse module needs to be
> available when mount.glusterfs is invoked. This can be achieved in one
> of two ways:
>
> 1. Compile the module statically into the kernel.
> 2. Arrange for fuse service to be started prior to netmount (using say
> /etc/conf.d/netmount rc_need="fuse")
This doesn't sound right. Why does the kernel module need to be loaded
explicitly?
The kernel should auto-load the module when /dev/fuse is opened for
the first time.
/dev/fuse should get created via tmpfiles.d via kmod-static-nodes.
prev parent reply other threads:[~2024-04-11 15:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-08 9:51 [gentoo-dev] netmount and glusterfs (fuse) dependency management Jaco Kroon
2024-04-11 5:11 ` Joonas Niilola
2024-04-11 6:14 ` Jaco Kroon
2024-04-11 10:02 ` Joonas Niilola
2024-04-11 12:26 ` Jaco Kroon
2024-04-11 15:53 ` Mike Gilbert [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=CAJ0EP42P6W5tFVFag912KYyuKHhSfT5jfx_Qsek9wK2nnVXw0Q@mail.gmail.com \
--to=floppym@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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