On 02/18/2010 06:01 PM, Roland Fischer wrote:
Hi harshavardhana,
thank you for your reply. We have turned off option mandatory-locks
but error is the same.
What means this error?
[2010-02-16 11:54:27] E [afr.c:179:afr_read_child] mirror: invalid
argument: inode
[2010-02-16 11:54:27] E [afr.c:179:afr_read_child] mirror: invalid
argument: inode
[2010-02-16 11:54:27] E [afr.c:179:afr_read_child] mirror: invalid
argument: inode
[2010-02-16 11:54:27] E [afr.c:179:afr_read_child] mirror: invalid
argument: inode
[2010-02-16 11:54:27] E [afr.c:179:afr_read_child] mirror: invalid
argument: inode
[2010-02-16 11:54:27] E [afr.c:179:afr_read_child] mirror: invalid
argument: inode
[2010-02-16 11:54:27] E [afr.c:179:afr_read_child] mirror: invalid
argument: inode
volume locks
type features/locks
option mandatory-locks on
Is there a reason why this has been switched on?. Does your
application does mandatory locking?.
Please read through
"http://gluster.com/community/documentation/index.php/Translators/features/locks";
the NOTE to get the exact behaviour of using this.
Thank you
roland
Roland,
can you file a bug at our bugzilla with relevant log files and
volume files so that we can work/ understand the problem. Please make
sure that you attach full log files. Including kernel, fuse and
glusterfs version details.
Thanks
--
Harshavardhana
http://www.gluster.com
