gluster-kubernetes icon indicating copy to clipboard operation
gluster-kubernetes copied to clipboard

Published 20 hours ago • verified publisher icon gluster

tune2fs not found in image 3.10

Open grig-tar opened this issue 6 years ago • 3 comments

Image gluster-centos:gluster3u10_centos7

/var/log/glusterfs/glusterd.log:

The message "I [MSGID: 106488] [glusterd-handler.c:1538:__glusterd_handle_cli_get_volume] 0-management: Received get vol req" repeated 55 times between [2019-04-15 06:26:52.792105] and [2019-04-15 06:28:26.197988]
The message "E [MSGID: 106419] [glusterd-utils.c:6161:glusterd_add_inode_size_to_dict] 0-management: could not find tune2fs to getinode size for /dev/xvda1 (ext4): e2fsprogs package missing?" repeated 11 times between [2019-04-15 06:27:04.241409] and [2019-04-15 06:28:43.324361]
The message "I [MSGID: 106487] [glusterd-handler.c:1475:__glusterd_handle_cli_list_friends] 0-glusterd: Received cli list req" repeated 3 times between [2019-04-15 06:27:17.970440] and [2019-04-15 06:28:48.388905]
[2019-04-15 06:28:57.377301] I [MSGID: 106488] [glusterd-handler.c:1538:__glusterd_handle_cli_get_volume] 0-management: Received get vol req
[2019-04-15 06:28:59.225133] E [MSGID: 106419] [glusterd-utils.c:6161:glusterd_add_inode_size_to_dict] 0-management: could not find tune2fs to getinode size for /dev/xvda1 (ext4): e2fsprogs package missing?
[2019-04-15 06:29:18.594354] I [MSGID: 106487] [glusterd-handler.c:1475:__glusterd_handle_cli_list_friends] 0-glusterd: Received cli list req

tune2fs is missing in image

grig-tar avatar Apr 17 '19 16:04 grig-tar

Are you using ext4 file systems? If so, how? IIRC if you're using the gluster-kubernetes stack everything (in particular heketi) should use xfs. Unless you're creating bricks manually?

phlogistonjohn avatar Apr 17 '19 18:04 phlogistonjohn

I have two devices:

  • xvda - one partition xvda1, ext4, OS installed here
  • xvdb - two partitions:
    • xvdb1 - used for manually backups
    • xvdb2 - provided to heketi

I don't know why gluster trying to get info about xvda.

grig-tar avatar Apr 18 '19 08:04 grig-tar

Ah, very odd. In this case I can only suggest verifying that all brick filesystems are mounted and that gluster isn't accidentally looking at an unmounted mount point where a brick should be. Once verified, assuming all bricks are mounted as should be I'd ask about this in one of the gluster forums.

phlogistonjohn avatar Apr 18 '19 13:04 phlogistonjohn