Gluster users - Mar 2017 - Any way to get rid of zfs error messages?

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

Could you file a bug and paste the command and output in there? We can
then add it for a 3.8 update.
 
https://bugzilla.redhat.com/enter_bug.cgi?product=GlusterFS&version=3.8&component=glusterd

Of course, patches are welcome too :-)
 
http://gluster.readthedocs.io/en/latest/Developer-guide/Simplified-Development-Workflow/

Thanks,
Niels
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL:
<http://lists.gluster.org/pipermail/gluster-users/attachments/20170306/dffe900f/attachment.sig>

Hi Niels,

Is this bug got fix on the version 3.9.0?

Thanks,
~ Vic Le
> On Mar 6, 2017, at 12:36 PM, Niels de Vos <ndevos at redhat.com>
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
> 
> Could you file a bug and paste the command and output in there? We can
> then add it for a 3.8 update.
> 
https://bugzilla.redhat.com/enter_bug.cgi?product=GlusterFS&version=3.8&component=glusterd
> 
> Of course, patches are welcome too :-)
> 
http://gluster.readthedocs.io/en/latest/Developer-guide/Simplified-Development-Workflow/
> 
> Thanks,
> Niels
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-users

On Mon, Mar 06, 2017 at 01:06:36PM -0800, Dung Le wrote:
> Hi Niels,
> 
> Is this bug got fix on the version 3.9.0?
No, it needs to get fixed in the master branch, and then we can backport
the fix to the maintained versions. GlusterFS 3.9 is not maintained
anymore since 3.10 is released, and I do not expect that there will be
any further 3.9 updates.

The current versions that we maintain, are 3.8 and 3.10. More details
about the Long-Term-Maintenance and Short-Term-Maintenance versions can
be found on https://www.gluster.org/community/release-schedule/

HTH,
Niels

> 
> Thanks,
> ~ Vic Le
> 
> > On Mar 6, 2017, at 12:36 PM, Niels de Vos <ndevos at redhat.com>
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
> > 
> > Could you file a bug and paste the command and output in there? We can
> > then add it for a 3.8 update.
> > 
https://bugzilla.redhat.com/enter_bug.cgi?product=GlusterFS&version=3.8&component=glusterd
> > 
> > Of course, patches are welcome too :-)
> > 
http://gluster.readthedocs.io/en/latest/Developer-guide/Simplified-Development-Workflow/
> > 
> > Thanks,
> > Niels
> > _______________________________________________
> > Gluster-users mailing list
> > Gluster-users at gluster.org
> > http://lists.gluster.org/mailman/listinfo/gluster-users
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL:
<http://lists.gluster.org/pipermail/gluster-users/attachments/20170306/4bd4d355/attachment.sig>

> On Mar 6, 2017, at 2:36 PM, Niels de Vos <ndevos at redhat.com>
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
<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?
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.gluster.org/pipermail/gluster-users/attachments/20170306/8ec08837/attachment.html>