<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Mar 6, 2017, at 2:36 PM, Niels de Vos <<a href="mailto:ndevos@redhat.com" class="">ndevos@redhat.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">On Mon, Mar 06, 2017 at 05:26:56PM +0100, Arman Khalatyan wrote:<br class=""><blockquote type="cite" class="">hi, I have replicated glusterfs on 3 nodes with zfs, the logs are flooded<br class="">with inodes error<br class=""><br class="">[2017-03-06 16:24:15.019386] E [MSGID: 106419]<br class="">[glusterd-utils.c:5458:glusterd_add_inode_size_to_dict] 0-management: could<br class="">not find (null) to getinode size for zclei21/01 (zfs): (null) package<br class="">missing?<br class=""><br class="">Any way to fix it?<br class=""><br class="">glusterfs --version<br class="">glusterfs 3.8.9 built on Feb 13 2017 10:03:47<br class=""></blockquote><br class="">We'll need to add the zfs command to fetch the size of the inodes. The<br class="">commands for the different filesystems that we currently recognize are<br class="">in the 'fs_info' structure at:<br class=""> <a href="https://github.com/gluster/glusterfs/blob/master/xlators/mgmt/glusterd/src/glusterd-utils.c#L5895" class="">https://github.com/gluster/glusterfs/blob/master/xlators/mgmt/glusterd/src/glusterd-utils.c#L5895</a><br class=""></div></div></blockquote></div><br class=""><div class="">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?</div></body></html>