<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN">
<html><body>
<p>Osborne, Paul (paul.osborne@canterbury.ac.uk) писал 2015-03-16 19:22:</p>
<blockquote type="cite" style="padding-left:5px; border-left:#1010ff 2px solid; margin-left:5px; width:100%">
<div class="WordSection1">
<p class="MsoNormal">Hi,</p>
<p class="MsoNormal">I am just looking through my logs and am seeing a lot of entries of the form:</p>
<p class="MsoNormal">[2015-03-16 16:02:55.553140] I [glusterd-handler.c:3530:__glusterd_handle_status_volume] 0-management: Received status volume req for volume wiki</p>
<p class="MsoNormal">[2015-03-16 16:02:55.561173] E [glusterd-utils.c:5140:glusterd_add_inode_size_to_dict] 0-management: tune2fs exited with non-zero exit status</p>
<p class="MsoNormal">[2015-03-16 16:02:55.561204] E [glusterd-utils.c:5166:glusterd_add_inode_size_to_dict] 0-management: failed to get inode size</p>
<p class="MsoNormal">Having had a rummage I *<strong>suspect</strong>* it is because gluster is trying to get the volume status by querying the superblock on the filesystem for a brick volume. However this is an issue as when the volume was created it was done so in the form:</p>
</div>
</blockquote>
<div class="WordSection1">
<p class="MsoNormal">I believe it is a bug with tune2fs missed device argument, introduced this patch<br />http://review.gluster.org/#/c/8134/</p>
</div>
<div>
<pre>--
Vitaly Lipatov
Etersoft</pre>
</div>
</body></html>