Khoi,
On Thursday 03 April 2014 08:23 AM, Khoi Mai wrote:
Varun,
I don't believe I am ready to upgrade from 3.4.2-1 - > 3.5 yet. I
tried the (find . ) on the volume mount though a fuse client, and my
gluster server logs still log accessive amounts of the same message in
/var/log/glusterfs/bricks/dynamic-weblogic.log
[2014-04-03 02:49:33.098664] E
[marker-quota-helper.c:229:mq_dict_set_contribution]
(-->/usr/lib64/glusterfs/3.4.2/xlator/debug/io-stats.so(io_stats_lookup+0x157)
[0x7fb33f9ba2e7]
(-->/usr/lib64/glusterfs/3.4.2/xlator/features/marker.so(marker_lookup+0x2f8)
[0x7fb33fbcffc8]
(-->/usr/lib64/glusterfs/3.4.2/xlator/features/marker.so(mq_req_xattr+0x3c)
[0x7fb33fbd9f1c]))) 0-marker: invalid argument: loc->parent
[2014-04-03 02:49:33.122216] E
[marker-quota-helper.c:229:mq_dict_set_contribution]
(-->/usr/lib64/glusterfs/3.4.2/xlator/debug/io-stats.so(io_stats_lookup+0x157)
[0x7fb33f9ba2e7]
(-->/usr/lib64/glusterfs/3.4.2/xlator/features/marker.so(marker_lookup+0x2f8)
[0x7fb33fbcffc8]
(-->/usr/lib64/glusterfs/3.4.2/xlator/features/marker.so(mq_req_xattr+0x3c)
[0x7fb33fbd9f1c]))) 0-marker: invalid argument: loc->parent
is there any other way to prevent this from logging so much?
As I explained this is because the server can't find the inode of the
gfid the file operations corresponds to. There might be 2 reasons for that
i. Bricks are restarted and not yet populated the inode tree. This can
be solved by the previous solution we tried (find .).
ii. Even if the bricks are up and running, inode table may exceed its
limit and starts dropping the older inodes. This problem can be lessened
by increasing the inode table limit (may lru limit in gluster cli options).
Can you try the solution for the second problem?
Thanks
Varun Shastry
Khoi Mai
Union Pacific Railroad
Distributed Engineering & Architecture
Project Engineer
From: Varun Shastry <[email protected]>
To: Khoi Mai <[email protected]>, [email protected]
Date: 04/01/2014 06:21 AM
Subject: Re: [Gluster-users] i'm not sure how to solve this log file?
------------------------------------------------------------------------
Khoi,
This is because of the NFS nameless/gfid lookups. If bricks are
restarted while the NFS clients are still mounted it uses File Handles
(gfids in glusterfs) and performs the operations based on only FHs.
The bug is fixed in 3.5, so upgrading would solve the issue. Also a
crawl (find .) from fuse/native mount can resolve the issue until the
next restart of the bricks.
- Varun Shastry
On Sunday 30 March 2014 10:32 PM, Khoi Mai wrote:
[2014-03-30 17:00:39.330462] E
[marker-quota-helper.c:229:mq_dict_set_contribution]
(-->/usr/lib64/glusterfs/3.4.2/xlator/debug/io-stats.so(io_stats_lookup+0x157)
[0x7fe5642222e7]
(-->/usr/lib64/glusterfs/3.4.2/xlator/features/marker.so(marker_lookup+0x2f8)
[0x7fe564437fc8]
(-->/usr/lib64/glusterfs/3.4.2/xlator/features/marker.so(mq_req_xattr+0x3c)
[0x7fe564441f1c]))) 0-marker: invalid argument: loc->parent
[2014-03-30 17:00:39.336824] E
[marker-quota-helper.c:229:mq_dict_set_contribution]
(-->/usr/lib64/glusterfs/3.4.2/xlator/debug/io-stats.so(io_stats_lookup+0x157)
[0x7fe5642222e7]
(-->/usr/lib64/glusterfs/3.4.2/xlator/features/marker.so(marker_lookup+0x2f8)
[0x7fe564437fc8]
(-->/usr/lib64/glusterfs/3.4.2/xlator/features/marker.so(mq_req_xattr+0x3c)
[0x7fe564441f1c]))) 0-marker: invalid argument: loc->parent
[2014-03-30 17:00:39.358222] E
[marker-quota-helper.c:229:mq_dict_set_contribution]
(-->/usr/lib64/glusterfs/3.4.2/xlator/debug/io-stats.so(io_stats_lookup+0x157)
[0x7fe5642222e7]
(-->/usr/lib64/glusterfs/3.4.2/xlator/features/marker.so(marker_lookup+0x2f8)
[0x7fe564437fc8]
(-->/usr/lib64/glusterfs/3.4.2/xlator/features/marker.so(mq_req_xattr+0x3c)
[0x7fe564441f1c]))) 0-marker: invalid argument: loc->parent
[2014-03-30 17:00:39.396809] E
[marker-quota-helper.c:229:mq_dict_set_contribution]
(-->/usr/lib64/glusterfs/3.4.2/xlator/debug/io-stats.so(io_stats_lookup+0x157)
[0x7fe5642222e7]
(-->/usr/lib64/glusterfs/3.4.2/xlator/features/marker.so(marker_lookup+0x2f8)
[0x7fe564437fc8]
(-->/usr/lib64/glusterfs/3.4.2/xlator/features/marker.so(mq_req_xattr+0x3c)
[0x7fe564441f1c]))) 0-marker: invalid argument: loc->parent
[2014-03-30 17:00:39.413244] E
[marker-quota-helper.c:229:mq_dict_set_contribution]
(-->/usr/lib64/glusterfs/3.4.2/xlator/debug/io-stats.so(io_stats_lookup+0x157)
[0x7fe5642222e7]
(-->/usr/lib64/glusterfs/3.4.2/xlator/features/marker.so(marker_lookup+0x2f8)
[0x7fe564437fc8]
(-->/usr/lib64/glusterfs/3.4.2/xlator/features/marker.so(mq_req_xattr+0x3c)
[0x7fe564441f1c]))) 0-marker: invalid argument: loc->parent
[2014-03-30 17:00:39.484909] E
[marker-quota-helper.c:229:mq_dict_set_contribution]
(-->/usr/lib64/glusterfs/3.4.2/xlator/debug/io-stats.so(io_stats_lookup+0x157)
[0x7fe5642222e7]
(-->/usr/lib64/glusterfs/3.4.2/xlator/features/marker.so(marker_lookup+0x2f8)
[0x7fe564437fc8]
(-->/usr/lib64/glusterfs/3.4.2/xlator/features/marker.so(mq_req_xattr+0x3c)
[0x7fe564
It continues to fill up my
/var/log/glusterfs/bricks/dynamic-weblogic.log file, Can someobdy
help me interpret the messages and possible what would be the fix?
Khoi Mai
Union Pacific Railroad
Distributed Engineering & Architecture
Project Engineer
**
This email and any attachments may contain information that is
confidential and/or privileged for the sole use of the intended
recipient. Any use, review, disclosure, copying, distribution or
reliance by others, and any forwarding of this email or its contents,
without the express permission of the sender is strictly prohibited by
law. If you are not the intended recipient, please contact the sender
immediately, delete the e-mail and destroy all copies.
**
_______________________________________________
Gluster-users mailing list
[email protected]_ <mailto:[email protected]>
_http://supercolony.gluster.org/mailman/listinfo/gluster-users_
**
This email and any attachments may contain information that is
confidential and/or privileged for the sole use of the intended
recipient. Any use, review, disclosure, copying, distribution or
reliance by others, and any forwarding of this email or its contents,
without the express permission of the sender is strictly prohibited by
law. If you are not the intended recipient, please contact the sender
immediately, delete the e-mail and destroy all copies.
**
_______________________________________________
Gluster-users mailing list
[email protected]
http://supercolony.gluster.org/mailman/listinfo/gluster-users
