<html>
<head>
<meta content="text/html; charset=ISO-8859-2"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi,<br>
<br>
Thank you I haven't seen this article. But we use Centos 5 and
ext3 on every machine.<br>
<br>
Br,<br>
Adam<br>
<br>
<div class="moz-signature">
<div style="font-family: Arial, sans-serif; color: #000000;">
<span style="font-size: 14px; color: #E32407;">
</span><span style="font-size: 10px; color: ##000000"><a
style="font-size: 11px; color: #E32407 !important;"
href="http://www.virtual-call-center.hu"></a><br>
</span>
</div>
</div>
2013-05-03 11:08 keltezéssel, Joe Julian írta:<br>
</div>
<blockquote cite="mid:51837EA0.4080000@julianfamily.org" type="cite">
<meta content="text/html; charset=ISO-8859-2"
http-equiv="Content-Type">
<div class="moz-cite-prefix">On 05/03/2013 12:52 AM, Koleszár Ádám
wrote:<br>
</div>
<blockquote cite="mid:51836CD6.5030505@virtual-call-center.eu"
type="cite">Hi, <br>
<br>
<br>
We have a problem with glusterFS. We are using it on Centos 5
machine with OpenVZ kernel. Gluster daemon and gluster clients
run on the host, not in the container. Recently we noticed a
problem when we upgraded the OpenVZ kernel. After the upgrade
there are strange errors in case of accessing the gluster
volume. There are a few folders that can't be seen with 'ls' but
if you give the whole path you can access the files in the
folder. If there is a folder with files in it and you type 'ls'
it hangs and only can be stopped with 'kill -9'. <br>
<br>
We are using glusterfs 3.2.5 but we have tried with 3.2.7 and
the same happened. <br>
With kernel version: 2.6.18-308.el5.028stab099.3 -- there were
no errors. <br>
With kernel version: 2.6.18-348.3.1.el5.028stab106.2 -- it has
the above mentioned errors <br>
<br>
Unfortunately we don't have any information about the other
kernels between the two versions. We can reproduce the errors in
production and development environments. We created a new volume
on our own test computers but we cannot reproduce the bugs. If
we mount the development gluster volume on the test computers
which are running the 2.6.18-348.3.1.el5.028stab106.2 OVZ kernel
we cannot reproduce the bug. That's why we think the gluster
clients work with the new kernel but the gluster daemon doesn't.
<br>
<br>
</blockquote>
It's the ext4 problem:
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-2">
<a moz-do-not-send="true"
href="http://joejulian.name/blog/glusterfs-bit-by-ext4-structure-change/">http://joejulian.name/blog/glusterfs-bit-by-ext4-structure-change/</a><br>
<br>
Backported to el5 as of 2.6.18-326.el5
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-2">
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Gluster-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a>
<a class="moz-txt-link-freetext" href="http://supercolony.gluster.org/mailman/listinfo/gluster-users">http://supercolony.gluster.org/mailman/listinfo/gluster-users</a></pre>
</blockquote>
<br>
</body>
</html>