<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style id="owaParaStyle" type="text/css">
<!--
p
{margin-top:0;
margin-bottom:0}
p
{margin-top:0;
margin-bottom:0}
p
{margin-top:0;
margin-bottom:0}
-->
P {margin-top:0;margin-bottom:0;}</style>
</head>
<body ocsi="0" fpstyle="1">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">I've now tried the same repeater scenario against EXT2, EXT3, EXT4, and XFS formatted bricks. There's no change in behavior; the discriminating detail is still only whether the
build-pgfid volume option is on. Number of bricks, distribution over servers, transport protocol, etc., can all be changed over a wide range without affecting the scope or nature of failure.<br>
<br>
Is there anyone using build-pgfid=on, doing any fine-grained small-file I/O (such as building sizable project from source), and *not* getting xattr errors in the brick logs / undeletable files due to incomplete xattr ops? Anyone? Anyone? Buhler? Buhler?<br>
<br>
<br>
<div style="font-family: Times New Roman; color: #000000; font-size: 16px">
<hr tabindex="-1">
<div style="direction: ltr;" id="divRpF486050"><font face="Tahoma" color="#000000" size="2"><b>From:</b> LaGarde, Owen M ERDC-RDE-ITL-MS Contractor<br>
<b>Sent:</b> Friday, November 13, 2015 4:36 PM<br>
<b>To:</b> gluster-users@gluster.org; LaGarde, Owen M ERDC-RDE-ITL-MS Contractor<br>
<b>Subject:</b> RE: 'No data available' at clients, brick xattr ops errors on small I/O -- XFS stripe issue or repeat bug?<br>
</font><br>
</div>
<div></div>
<div>
<div style="direction:ltr; font-family:Tahoma; color:#000000; font-size:10pt">Looks like the errors occur only when the gfid-to-path translation [volume option] is on. Is anyone else seeing this? Anyone using 3.6.6-1 with XFS-formatted bricks?<br>
<br>
<br>
<div style="font-family:Times New Roman; color:#000000; font-size:16px">
<hr tabindex="-1">
<div id="divRpF391260" style="direction:ltr"><font face="Tahoma" color="#000000" size="2"><b>From:</b> LaGarde, Owen M ERDC-RDE-ITL-MS Contractor<br>
<b>Sent:</b> Tuesday, November 10, 2015 4:24 PM<br>
<b>To:</b> gluster-users@gluster.org; LaGarde, Owen M ERDC-RDE-ITL-MS Contractor<br>
<b>Subject:</b> RE: 'No data available' at clients, brick xattr ops errors on small I/O -- XFS stripe issue or repeat bug?<br>
</font><br>
</div>
<div></div>
<div>
<div style="direction:ltr; font-family:Tahoma; color:#000000; font-size:10pt">Update: I've tried a second cluster with AFAIK identical backing storage configuration from the LUNs up, identical gluster/xfsprogs/kernel on the servers, identical volume setup,
and identical kernel/gluster on the clients. The reproducer does not fail on the new system. So far I can't find any delta between the two clusters' setup other than the brick count (28 bricks across 8 servers on the failing one, 14 bricks across 4 servers
on the new one).<br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>