On Fri, Dec 14, 2018 at 11:49 AM wrote:
> Hi,
>
>
>
> We updated our glusterfs servers and clients from 3.10 to 4.1.6. Although
> all seems to be working just fine we see errors like these on almost all
> glusterfs servers:
>
>
>
> [2018-12-14 02:35:03.524378] I
Hi,
We updated our glusterfs servers and clients from 3.10 to 4.1.6. Although all
seems to be working just fine we see errors like these on almost all glusterfs
servers:
[2018-12-14 02:35:03.524378] I [addr.c:55:compare_addr_and_update]
0-/apps/glusterfs-gst: allowed = "*", received addr =
On Thu, 2018-12-13 at 15:31 +, Matt Waymack wrote:
> Hi all,
>
> I’m having an issue on Windows clients accessing shares via smb when
> using vfs_glusterfs. They are unable to create any file or folders
> at the root of the share and get the error “The file is too large for
> the
On 12/13/18 2:13 PM, Lindolfo Meira wrote:
> Links for OpenSUSE Leap packages never work :/
I assume you are trying the link at [3]
IOW,
http://download.opensuse.org/repositories/home:/glusterfs:/Leap15-5/openSUSE_Leap_15/
That did not take me anywhere as well, but on backtracking the right
Links for OpenSUSE Leap packages never work :/
What gives?
Lindolfo Meira, MSc
Diretor Geral, Centro Nacional de Supercomputação
Universidade Federal do Rio Grande do Sul
+55 (51) 3308-3122
On Thu, 13 Dec 2018, Shyam Ranganathan wrote:
> The Gluster community is pleased to announce the
The Gluster community is pleased to announce the release of Gluster
5.2 (packages available at [1]).
Release notes can be found at [2].
Major changes, features and limitations addressed in this release:
- Several bugs as listed in the release notes have been addressed
Thanks,
Gluster community
Hi,
is there a way to recover file from "Stale file handle" errors?
Here some of the tests we have done:
- compared the extended attributes of all of the three replicas of the
involved shard. Found identical attributes.
- compared SHA512 message digest of all of the three replicas of the
Hi all,
I'm having an issue on Windows clients accessing shares via smb when using
vfs_glusterfs. They are unable to create any file or folders at the root of
the share and get the error "The file is too large for the destination file
system." When I change from vfs_glusterfs to just using a
Am 12.12.18 um 16:13 schrieb Stefan Kania:
> Me again :-)
>
> Am 12.12.18 um 14:53 schrieb Stefan Kania:
>> I have configured geo-replication with a non-privileged user, I used
>> this documentation:
>
> I now set up the geo-replication with user root and everything worked.
> So it must have
