Bug 1346226
Summary: | [Tiering]: unable to mount a tiered volume from rhel-5 client | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | krishnaram Karthick <kramdoss> |
Component: | tier | Assignee: | Bug Updates Notification Mailing List <rhs-bugs> |
Status: | CLOSED WONTFIX | QA Contact: | Nag Pavan Chilakam <nchilaka> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | rhgs-3.1 | CC: | dlambrig, p.stukalov, rcyriac, rhs-bugs, storage-qa-internal |
Target Milestone: | --- | Keywords: | ZStream |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-06-16 13:48:36 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
krishnaram Karthick
2016-06-14 10:12:37 UTC
It appears the version of sqlite shipped in RHEL5 does not have certain interfaces we use in the gfdb library. To fix this we would have to remove the usage of those interfaces and revert to older code. The ones I found were: sqlite3_open_v2() and sqlite3_prepare_v2(). This may be disruptive to the current code base. We do not plan to fix this. The bug can be reopened if this supported is needed. Hello. I have this problem on Centos7 [2019-04-25 10:45:49.631018] I [glusterfsd.c:2556:daemonize] 0-glusterfs: Pid of current running process is 20374 [2019-04-25 10:45:49.642692] I [MSGID: 101190] [event-epoll.c:680:event_dispatch_epoll_worker] 0-epoll: Started thread with index 0 [2019-04-25 10:45:49.642763] I [MSGID: 101190] [event-epoll.c:680:event_dispatch_epoll_worker] 0-epoll: Started thread with index 1 [2019-04-25 10:45:49.650056] W [MSGID: 101095] [xlator.c:374:xlator_dynload] 0-xlator: /usr/lib64/glusterfs/6.1/xlator/cluster/tier.so: невозможно открыть разделяемый объектный файл: Нет такого файла или каталога [2019-04-25 10:45:49.650093] E [MSGID: 101002] [graph.y:213:volume_type] 0-parser: Volume 'freezer-tier-dht', line 680: type 'cluster/tier' is not valid or not found on this machine [2019-04-25 10:45:49.650114] E [MSGID: 101019] [graph.y:321:volume_end] 0-parser: "type" not specified for volume freezer-tier-dht [2019-04-25 10:45:49.650524] E [MSGID: 100026] [glusterfsd.c:2636:glusterfs_process_volfp] 0-: failed to construct the graph [2019-04-25 10:45:49.650864] W [glusterfsd.c:1570:cleanup_and_exit] (-->/usr/sbin/glusterfs(mgmt_getspec_cbk+0x8a1) [0x5637acdb8ad1] -->/usr/sbin/glusterfs(glusterfs_process_volfp+0x249) [0x5637acdb1cb9] -->/usr/sbin/glusterfs(cleanup_and_exit+0x6b) [0x5637acdb106b] ) 0-: received signum (-1), shutting down [2019-04-25 10:45:49.650900] I [fuse-bridge.c:6807:fini] 0-fuse: Unmounting '/mnt'. [2019-04-25 10:45:49.657254] I [fuse-bridge.c:6812:fini] 0-fuse: Closing fuse connection to '/mnt'. [2019-04-25 10:45:49.657401] W [glusterfsd.c:1570:cleanup_and_exit] (-->/lib64/libpthread.so.0(+0x7dd5) [0x7f6d8dd11dd5] -->/usr/sbin/glusterfs(glusterfs_sigwaiter+0xe5) [0x5637acdb1205] -->/usr/sbin/glusterfs(cleanup_and_exit+0x6b) [0x5637acdb106b] ) 0-: received signum (15), shutting down [root@dtln-ceph04 ~]# uname -a Linux dtln-ceph04 3.10.0-957.10.1.el7.x86_64 #1 SMP Mon Mar 18 15:06:45 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux [root@dtln-ceph04 ~]# cat /etc/redhat-release CentOS Linux release 7.6.1810 (Core) [root@dtln-ceph04 ~]# gluster --version glusterfs 6.1 Repository revision: git://git.gluster.org/glusterfs.git Copyright (c) 2006-2016 Red Hat, Inc. <https://www.gluster.org/> GlusterFS comes with ABSOLUTELY NO WARRANTY. It is licensed to you under your choice of the GNU Lesser General Public License, version 3 or any later version (LGPLv3 or later), or the GNU General Public License, version 2 (GPLv2), in all cases as published by the Free Software Foundation. Can this be fixed ? |