Aggregating distributed file system

Edit Package glusterfs

GlusterFS is a clustered file-system capable of scaling to several
petabytes. It aggregates various storage bricks over Infiniband RDMA
or TCP/IP interconnect into one large parallel network file system.
GlusterFS is one of the most sophisticated file systems in terms of
features and extensibility. It borrows a powerful concept called
Translators from GNU Hurd kernel. Much of the code in GlusterFS is in
user space and easily manageable.

Refresh
Refresh
Source Files
Filename Size Changed
glusterfs-3.5.2.tar.gz 0004972250 4.74 MB
glusterfs-date.diff 0000002837 2.77 KB
glusterfs.changes 0000007716 7.54 KB
glusterfs.spec 0000007990 7.8 KB
Revision 12 (latest revision is 39)
Ludwig Nussel's avatar Ludwig Nussel (lnussel) accepted request 243925 from Jan Engelhardt's avatar Jan Engelhardt (jengelh) (revision 12)
- Update to new upstream release 3.5.2
  * NFS server crashes in _socket_read_vectored_request
  * Can't write to quota enable folder
  * nfs: reset command does not alter the result for nfs options earlier set
  * features/gfid-access: stat on .gfid virtual directory return EINVAL
  * creating symlinks generates errors on stripe volume
  * Self-heal errors with "afr crawl failed for child 0 with ret -1" while performing rolling upgrade.
  * [AFR] I/O fails when one of the replica nodes go down
  * Fix inode leaks in gfid-access xlator
  * NFS subdir authentication doesn't correctly handle multi-(homed,protocol,etc) network addresses
  * nfs-utils should be installed as dependency while installing glusterfs-server
  * Excessive logging in quotad.log of the kind 'null client'
  * client_t clienttable cliententries are never expanded when all entries are used
  * AFR : self-heal of few files not happening when a AWS EC2 Instance is back online after a restart
  * Dist-geo-rep : deletion of files on master, geo-rep fails to propagate to slaves.
  * Allow the usage of the wildcard character '*' to the options
    "nfs.rpc-auth-allow" and "nfs.rpc-auth-reject"
  * glfsheal: Improve the way in which we check the presence of replica volumes
  * Resource cleanup doesn't happen for clients on servers after disconnect
  * mounting a volume over NFS (TCP) with MOUNT over UDP fails
  * backport 'gluster volume status --xml' issues
  * Glustershd memory usage too high (forwarded request 243914 from scorot)
Comments 2

Michael Traxler's avatar
The glusterd crashes when started:

$ systemctl restart glusterd.service the message in the journal is:

    May 10 01:05:42 l10 systemd[1]: Starting GlusterFS, a clustered file-system server...
    May 10 01:05:42 l10 glusterd[5203]: Fatal glibc error: malloc.c:2593 (sysmalloc): assertion failed: (old_top == initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_\
inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)
    May 10 01:05:42 l10 systemd[1]: Started Process Core Dump (PID 5204/UID 0).
    May 10 01:05:42 l10 systemd-coredump[5205]: [🡕] Process 5203 (glusterd) of user 0 dumped core.

                                            Stack trace of thread 5203:
                                            #0  0x00007f2daed5d90c __pthread_kill_implementation (libc.so.6 + 0x8f90c)
                                            #1  0x00007f2daed0c196 raise (libc.so.6 + 0x3e196)
                                            #2  0x00007f2daecf4897 abort (libc.so.6 + 0x26897)
                                            #3  0x00007f2daecf5611 __libc_message.cold (libc.so.6 + 0x27611)
                                            #4  0x00007f2daed042e7 __libc_assert_fail (libc.so.6 + 0x362e7)
                                            #5  0x00007f2daed6af4c sysmalloc (libc.so.6 + 0x9cf4c)
                                            #6  0x00007f2daed6bef3 _int_malloc (libc.so.6 + 0x9def3)
                                            #7  0x00007f2daed6c90a __libc_malloc (libc.so.6 + 0x9e90a)
                                            #8  0x00007f2daef8e205 mem_get_malloc (libglusterfs.so.0 + 0x4a205)
                                            #9  0x00007f2daef8e319 mem_get_calloc (libglusterfs.so.0 + 0x4a319)
                                            #10 0x00007f2daef713ff _gf_msg (libglusterfs.so.0 + 0x2d3ff)
                                            #11 0x00007f2daef71a00 _gf_smsg (libglusterfs.so.0 + 0x2da00)
                                            #12 0x0000564fc3e1490a main (glusterfsd + 0x790a)
                                            #13 0x00007f2daecf5bb0 __libc_start_call_main (libc.so.6 + 0x27bb0)
                                            #14 0x00007f2daecf5c79 __libc_start_main@[@GLIBC\_2.34](https://build.opensuse.org/users/GLIBC_2.34) (libc.so.6 + 0x27c79)
                                            #15 0x0000564fc3e16735 _start (glusterfsd + 0x9735)
                                            ELF object binary architecture: AMD x86-64
    May 10 01:05:42 l10 systemd[1]: glusterd.service: Control process exited, code=dumped, status=6/ABRT
    May 10 01:05:42 l10 systemd[1]: glusterd.service: Failed with result 'core-dump'.
    May 10 01:05:42 l10 systemd[1]: Failed to start GlusterFS, a clustered file-system server.

I can only get glusterd to work when compiling it from the sources and with some hand work, please have a look to: https://bugzilla.suse.com/show_bug.cgi?id=1209702


Lindolfo Meira's avatar

Just found out about this. Freshly installed Tumbleweed and GlusterFS still not working. Does anyone have any news about it?

openSUSE Build Service is sponsored by