Hi Pranith and all,
I am not entirely sure what you mean by "how to trigger" the second problem.
This problem always occurs. I simply create a folder called test and
perform an rm -rf on this folder. I get the error message
rm: cannot remove directory `test/': No such file or directory
but the folder vanishes anyway.
About the first problem again: When you say, non-primary group
membership is treated as "others", this can't explain, as far as I
understand, why sometimes writing into the very same directoy works and
sometimes it fails. By the way: where can I see the bug reports?
Issuing a chown -R <user>:<primary_group> should resolve these issues,
shouldn't it?
Thanks for your help,
Daniel
On 01/28/2011 09:32 AM, Pranith Kumar. Karampuri wrote:
hi Daniel,
The first problem seems like bug 2296. Non-primary group membership was treated as
"other". It is already resolved and will be available in 3.1.3. Do you know how
to trigger the second problem?.
Pranith.
----- Original Message -----
From: "Daniel Zander"<zan...@ekp.uni-karlsruhe.de>
To: gluster-users@gluster.org
Sent: Friday, January 28, 2011 1:53:14 PM
Subject: [Gluster-users] GlusterFS 3.1.1: "Permission denied" and "No such
file or directory"
Dear all,
since the upgrade from glusterFS 3.0.0 to 3.1.1, some users have
experienced strange problems. When they want to create a folder or a
file, this usually works, but sometimes, it doesn't. The error message
is something like "Permission Denied".
The permissions and ownership of the affected folders seem to be set
correctly. I tried to chown -R user:group user/ anyway and it helped
once. It even occurs that when jobs try to write output back from our
batch system, most jobs can write files that are accessible, but a small
number cannot write their output (to the same folder at the same time).
Another problem, that might be related to the ones above is that
whenever a users tries to delete a directory, the following message occurs:
rm: cannot remove directory `test/': No such file or directory
but the directory is deleted anyway.
I've also seen files, that seem to have no permissions at all, e.g.
----------T 2 root root 4.1K Jan 17 10:26 mc_jpsi
This can be fixed manually, but is still very strange.
About our setup:
Volume Name: lemmy
Type: Distribute
Status: Started
Number of Bricks: 5
Transport-type: tcp
Bricks:
Brick1: 192.168.101.249:/storage/4/cluster
Brick2: 192.168.101.248:/storage/5/cluster
Brick3: 192.168.101.250:/storage/6/cluster
Brick4: 192.168.101.247:/storage/7/cluster
Brick5: 192.168.101.246:/storage/8/cluster
There is sufficient space left on all bricks. The operating systems of
the servers are debian5 (once) and Ubuntu 10.04 server (4 times). The
bricks have different filesystems (ext4 and xfs).
Thanks and Best Regards,
Daniel
_______________________________________________
Gluster-users mailing list
Gluster-users@gluster.org
http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
_______________________________________________
Gluster-users mailing list
Gluster-users@gluster.org
http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
