[Bugs] [Bug 1743215] glusterd-utils: 0-management: xfs_info exited with non-zero exit status [Permission denied]

bugzilla at redhat.com bugzilla at redhat.com
Tue Oct 8 14:05:12 UTC 2019


bueche at netnea.com changed:

           What    |Removed                     |Added
                 CC|                            |bueche at netnea.com

--- Comment #3 from bueche at netnea.com ---

I'm victim of this bug as well. I run 6.5 on SLES 12. I went a little further
and patched /usr/sbin/xfs_info (bash script) to show the command executed.
First, the filesystems involved :

root at srv1:~ # df
Filesystem                     1K-blocks     Used Available Use% Mounted on
not relevant
/dev/mapper/vgroot-lv_data     104806400 39871108  64935292  39% /data
srv1:repl-vol          104806400 40919172  63887228  40%

The command : 

/usr/sbin/gluster volume status repl-vol srv1:/data/glusterfs/vol0/brick0

Status of volume: repl-vol
Brick                : Brick srv1:/data/glusterfs/vol0/brick0
Inode Size           : N/A                 


log file glusterd.log :

[2019-10-08 14:00:47.819517] I [MSGID: 106499]
[glusterd-handler.c:4429:__glusterd_handle_status_volume] 0-management:
Received status volume req for volume repl-vol
[2019-10-08 14:00:47.838388] E [MSGID: 106419]
[glusterd-utils.c:6998:glusterd_add_inode_size_to_dict] 0-management: Unable to
retrieve inode size using xfs_info
[2019-10-08 14:00:47.838416] E [MSGID: 106419]
[glusterd-utils.c:7016:glusterd_add_inode_size_to_dict] 0-management: failed to
get inode size


and here it is ::: the command forked by glusterd-utils is using the wrong data
: the device instead of the mount point :

root at srv1:~ # xfs_growfs -p xfs_info -n  "/dev/mapper/vgroot-lv_data"
xfs_info: /dev/mapper/vgroot-lv_data is not a mounted XFS filesystem

It should be

root at srv1:~ # xfs_growfs -p xfs_info -n  "/data"                     
meta-data=/dev/mapper/vgroot-lv_data isize=512    agcount=4, agsize=6553600
         =                       sectsz=512   attr=2, projid32bit=1

So I think it uses the wrong argument passed to xfs_info.

You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.

More information about the Bugs mailing list