Re: Any way to get rid of zfs error messages?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On Mar 6, 2017, at 2:36 PM, Niels de Vos <ndevos@xxxxxxxxxx> wrote:

On Mon, Mar 06, 2017 at 05:26:56PM +0100, Arman Khalatyan wrote:
hi, I have replicated glusterfs on 3 nodes with zfs, the logs are flooded
with inodes error

[2017-03-06 16:24:15.019386] E [MSGID: 106419]
[glusterd-utils.c:5458:glusterd_add_inode_size_to_dict] 0-management: could
not find (null) to getinode size for zclei21/01 (zfs): (null) package
missing?

Any way to fix it?

glusterfs --version
glusterfs 3.8.9 built on Feb 13 2017 10:03:47

We'll need to add the zfs command to fetch the size of the inodes. The
commands for the different filesystems that we currently recognize are
in the 'fs_info' structure at:
 https://github.com/gluster/glusterfs/blob/master/xlators/mgmt/glusterd/src/glusterd-utils.c#L5895

ZFS “doesn’t have inodes” and thus there is no way to get their size. Would it be appropriate to treat it like Btrfs dynamic inodes, gluster wise? Would adding “zfs, NULL, NULL, NULL, NULL” to the detect code avoid those errors?
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-users

[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux