Hi, <br> A file can't "ls " ,but can "less ".<br> I think this action is a little weird. If this action can not be supported, an error may be <br>more friendly.<br><br><br>Baggio<br><br><br><div class="gmail_quote">
2008/7/4 Anand Avati <<a href="mailto:avati@zresearch.com">avati@zresearch.com</a>>:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
this case is considered equal to 'altering the backend without the mount point'. currently it is an unsupported 'action'.<br>
<br>
avati<div><div></div><div class="Wj3C7c"><br><br><div><span class="gmail_quote">On 03/07/2008, <b class="gmail_sendername">Arnulf Heimsbakk</b> <<a href="mailto:arnulf.heimsbakk@gmail.com" target="_blank">arnulf.heimsbakk@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<br> <br> I find GlusterFS as a refreshing alternative to traditional cluster<br> file systems. I have currently experimented with unify and AFR. When<br> experimenting with AFR with two bricks I found a strange behaviour. It<br>
seems that the directory is only read from the first brick.<br> <br> I created two bricks and run client side AFR. In the client config the<br> bricks is represented as follows:<br> <br> subvolumes brick1 brick2<br> <br>
Then I simulated a crash with loss of files.<br> <br> 1. AFR is up<br> 2. touch file f1<br> 3. brick1 crashes<br> 4. ls on mount point, f1 exists and everything is normal (ls read from brick2)<br> 5. file system repair removes f1 from brick1<br>
6. gclusterfsd start on brick1<br> 7. ls on mount point does not show f1 anymore (ls read only from brick1?)<br> 8. cat f1 on mount point replicates file and it becomes visible<br> <br> I have replicated this error a numerous times. Every time i have<br>
removed user_xattr from the exported directories.<br> <br> GlusterFS version 1.3.8<br> XFS backend filesystem<br> Debian Etch i686<br> <br> Is there a fix for this behaviour or is there a configuration solution<br> which eliminates this problem?<br>
Or is this problem considered to be a split brain case?<br> Does this affect AFRd namespaces (i did not test that)?<br> <br> Arnulf Heimsbakk<br> Sysadmin @ Norwegian Meteorological Institute<br> <br>--<br> "When all else fails, read the instructions." ~ L. Iasellio<br>
<br> _______________________________________________<br> Gluster-users mailing list<br> <a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br> <a href="http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users" target="_blank">http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users</a><br>
</blockquote></div><br><br clear="all"><br></div></div><font color="#888888">-- <br>If I traveled to the end of the rainbow<br>As Dame Fortune did intend,<br>Murphy would be there to tell me<br>The pot's at the other end.
</font><br>_______________________________________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
<a href="http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users" target="_blank">http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users</a><br>
<br></blockquote></div><br>