<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Are there any other requirements other than xattr support? Would be cool to find ever kernel fs impl and test them automatically on a server (maybe our rack space nodes) somewhere for a series of known gluster requirements.</div><div><br>On Apr 2, 2014, at 6:49 AM, Apostolos Manolitzas <<a href="mailto:manap@intracom-telecom.com">manap@intracom-telecom.com</a>> wrote:<br><br></div><blockquote type="cite"><div>
<meta content="text/html; charset=ISO-8859-7" http-equiv="Content-Type">
<div class="moz-cite-prefix">Hello,<br>
<br>
as far as I can see, from the UBIFS Faq
<a class="moz-txt-link-freetext" href="http://www.linux-mtd.infradead.org/doc/ubifs.html#L_xattr">http://www.linux-mtd.infradead.org/doc/ubifs.html#L_xattr</a><br>
<br>
UBIFS supports extended attributes if the corresponding
configuration option
is enabled (no additional mount options are required). It supports
the
<code>user</code>, <code>trusted</code>, and <code>security</code>
name-spaces.
However, access control lists (ACL) support is not implemented.<br>
<br>
beyond that, no clue if it's working.<br>
<br>
-Apostolos<br>
<br>
On 04/02/2014 02:41 PM, Carlos Capriotti wrote:<br>
</div>
<blockquote cite="mid:CAMShz31NvMYyst_LOCyjLXCgdRdZ6To3-aHg3QoeaCL9vYdCQg@mail.gmail.com" type="cite">
<div dir="ltr">Hi.
<div><br>
</div>
<div>i am not very familiar with those filesystems you
mentioned, but as a rule of thumb, a FS for gluster has to
support extended attributes, so, this is a good way to start:
check if you can tdo that.</div>
<div><br>
</div>
<div>Also, when setting gluster with the recommended
configuration, you are supposed to use XFS, and the inodes
have to be defined with -i size=512.</div>
<div><br>
</div>
<div>If experimenting with other FS, make sure you can set the
inode as well, just to be in the safe side.</div>
<div><br>
</div>
<div>EXT4 is not a good option right now, just in case you are
wondering. Lots of discussion and documentation on those
issues in past threads of the list.</div>
<div><br>
</div>
<div>Cheers.</div>
</div>
<div class="gmail_extra">
<br>
<br>
<div class="gmail_quote">On Wed, Apr 2, 2014 at 1:34 PM,
Apostolos Manolitzas <span dir="ltr"><<a moz-do-not-send="true" href="mailto:manap@intracom-telecom.com" target="_blank">manap@intracom-telecom.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"> Hello all,<br>
<br>
I just discovered the GlusterFS while looking for a
solution for high availability on our NAND flashes. We use
<a moz-do-not-send="true" href="http://en.wikipedia.org/wiki/Flash_file_system#Linux_flash_filesystems" target="_blank">ubifs</a> and <a moz-do-not-send="true" href="http://en.wikipedia.org/wiki/Flash_file_system#Linux_flash_filesystems" target="_blank">jffs2</a> for filesystem and we would
like to apply some high availability strategy to a part of
the flash. So has anyone tested GlusterFS with this setup?
Is it a viable solution or should we move to an upper
layer solution?<br>
<br>
thanks for any opinion,<br>
<br>
-Apostolos<br>
<br>
<br>
<br>
<br>
<br>
</div>
<br>
_______________________________________________<br>
Gluster-users mailing list<br>
<a moz-do-not-send="true" href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
<a moz-do-not-send="true" href="http://supercolony.gluster.org/mailman/listinfo/gluster-users" target="_blank">http://supercolony.gluster.org/mailman/listinfo/gluster-users</a><br>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
<br>
<br>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>Gluster-users mailing list</span><br><span><a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a></span><br><span><a href="http://supercolony.gluster.org/mailman/listinfo/gluster-users">http://supercolony.gluster.org/mailman/listinfo/gluster-users</a></span></div></blockquote></body></html>