Re: failed to get inode size in gluster log

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

 



On 06/20/2014 07:54 AM, Claudio Kuenzler wrote:
Hey Kaleb,

Thanks for your response.
Yes, the brick fs is ext4 (therefore the log entries "0-management:
tune2fs exited with non-zero exit status").

e2fsprogs package is installed. tune2fs command is also available.

By the way, I forgot to mention the version:
glusterfs 3.4.2
Ubuntu 14.04 LTS

What exactly is the glusterfs daemon trying to do? Does it just want to
get the information of how many inodes there are on the brick with
"tune2fs -l $brick"?

It's fetching the inode size for a `gluster volume info`, over and over and over again.

It should suffice to fetch it once and remember it.

I have a fix for this. Feel free to review it and help get it into the next version. See http://review.gluster.org/8134

--

Kaleb
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://supercolony.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