any advantage to using pool type glusterfs if no GFAPI
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: libvirt-users@xxxxxxxxxx
- Subject: any advantage to using pool type glusterfs if no GFAPI
- From: W Kern <wkmail@xxxxxxxxx>
- Date: Fri, 6 Oct 2023 13:23:18 -0700
- User-agent: Mozilla Thunderbird
I have used fuse mounted gluster with 'dir' for years. Works great,
aside from having to use the --unsafe flag on migrations.
I am building up a new system and wondering if using the glusterfs type
would be a better/safer choice.
I'm not concerned about gfapi (host is U22LTS so I'm not even sure if it
has it).
I'm not concerned about the automount feature as that happens on start
up anyway.
I'm more interested if there is any technical or performance reasons to
prefer 'glusterfs' pool type over 'dir'
of course not having the --unsafe flag would be nice, but thats all
scripted in anyway.
-wk
[Index of Archives]
[Virt Tools]
[Lib OS Info]
[Fedora Users]
[Fedora Desktop]
[Fedora SELinux]
[Yosemite News]
[KDE Users]