thr3ads.net - Gluster users - [Gluster-users] Repeative log messages, please help me interpret... [Dec 2013]

If this information is useful, please help other people find it:
Share via:

Khoi Mai

2013-Dec-01 15:56 UTC

[Gluster-users] Repeative log messages, please help me interpret...

Gluster community,


Ever since I've been running glusterfs3.4.1-3, log messages have gone out 
of control where I'd have 20G of space in /var and it gets filled up daily 
to 100% with the messages above.  Can someone please help me interpret the 
messages and suggest how I could resolve them?  My setup below is 2 node 
replicated volume.

Thank you,

kmai007

marker_lookup+0x2f8) [0x7fd954f7dfc8] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/features/marker.so(mq_req_xattr+0x3c) 
[0x7fd954f87f1c]))) 0-marker: invalid argument: loc->parent
[2013-12-01 02:22:28.529954] E 
[marker-quota-helper.c:229:mq_dict_set_contribution] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/debug/io-stats.so(io_stats_lookup+0x157)
[0x7fd954d682e7] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/features/marker.so(marker_lookup+0x2f8)
[0x7fd954f7dfc8] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/features/marker.so(mq_req_xattr+0x3c) 
[0x7fd954f87f1c]))) 0-marker: invalid argument: loc->parent
[2013-12-01 02:22:28.532913] E 
[marker-quota-helper.c:229:mq_dict_set_contribution] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/debug/io-stats.so(io_stats_lookup+0x157)
[0x7fd954d682e7] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/features/marker.so(marker_lookup+0x2f8)
[0x7fd954f7dfc8] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/features/marker.so(mq_req_xattr+0x3c) 
[0x7fd954f87f1c]))) 0-marker: invalid argument: loc->parent
[2013-12-01 02:22:28.534800] E 
[marker-quota-helper.c:229:mq_dict_set_contribution] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/debug/io-stats.so(io_stats_lookup+0x157)
[0x7fd954d682e7] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/features/marker.so(marker_lookup+0x2f8)
[0x7fd954f7dfc8] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/features/marker.so(mq_req_xattr+0x3c) 
[0x7fd954f87f1c]))) 0-marker: invalid argument: loc->parent
[2013-12-01 02:22:28.537790] E 
[marker-quota-helper.c:229:mq_dict_set_contribution] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/debug/io-stats.so(io_stats_lookup+0x157)
[0x7fd954d682e7] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/features/marker.so(marker_lookup+0x2f8)
[0x7fd954f7dfc8] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/features/marker.so(mq_req_xattr+0x3c) 
[0x7fd954f87f1c]))) 0-marker: invalid argument: loc->parent
[2013-12-01 02:22:28.540071] E 
[marker-quota-helper.c:229:mq_dict_set_contribution] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/debug/io-stats.so(io_stats_lookup+0x157)
[0x7fd954d682e7] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/features/marker.so(marker_lookup+0x2f8)
[0x7fd954f7dfc8] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/features/marker.so(mq_req_xattr+0x3c) 
[0x7fd954f87f1c]))) 0-marker: invalid argument: loc->parent
[2013-12-01 02:22:28.542266] E 
[marker-quota-helper.c:229:mq_dict_set_contribution] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/debug/io-stats.so(io_stats_lookup+0x157)
[0x7fd954d682e7] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/features/marker.so(marker_lookup+0x2f8)
[0x7fd954f7dfc8] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/features/marker.so(mq_req_xattr+0x3c) 
[0x7fd954f87f1c]))) 0-marker: invalid argument: loc->parent
[2013-12-01 02:22:28.544497] E 
[marker-quota-helper.c:229:mq_dict_set_contribution] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/debug/io-stats.so(io_stats_lookup+0x157)
[0x7fd954d682e7] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/features/marker.so(marker_lookup+0x2f8)
[0x7fd954f7dfc8] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/features/marker.so(mq_req_xattr+0x3c) 
[0x7fd954f87f1c]))) 0-marker: invalid argument: loc->parent
[2013-12-01 02:22:28.546424] E 
[marker-quota-helper.c:229:mq_dict_set_contribution] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/debug/io-stats.so(io_stats_lookup+0x157)
[0x7fd954d682e7] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/features/marker.so(marker_lookup+0x2f8)
[0x7fd954f7dfc8] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/features/marker.so(mq_req_xattr+0x3c) 
[0x7fd954f87f1c]))) 0-marker: invalid argument: loc->parent
[2013-12-01 02:22:28.549751] E 
[marker-quota-helper.c:229:mq_dict_set_contribution] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/debug/io-stats.so(io_stats_lookup+0x157)
[0x7fd954d682e7] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/features/marker.so(marker_lookup+0x2f8)
[0x7fd954f7dfc8] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/features/marker.so(mq_req_xattr+0x3c) 
[0x7fd954f87f1c]))) 0-marker: invalid argument: loc->parent
[2013-12-01 02:22:28.551996] E 
[marker-quota-helper.c:229:mq_dict_set_contribution] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/debug/io-stats.so(io_stats_lookup+0x157)
[0x7fd954d682e7] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/features/marker.so(marker_lookup+0x2f8)
[0x7fd954f7dfc8] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/features/marker.so(mq_req_xattr+0x3c) 
[0x7fd954f87f1c]))) 0-marker: invalid argument: loc->parent
[2013-12-01 02:22:28.554252] E 
[marker-quota-helper.c:229:mq_dict_set_contribution] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/debug/io-stats.so(io_stats_lookup+0x157)
[0x7fd954d682e7] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/features/marker.so(marker_lookup+0x2f8)
[0x7fd954f7dfc8] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/features/marker.so(mq_req_xattr+0x3c) 
[0x7fd954f87f1c]))) 0-marker: invalid argument: loc->parent
[2013-12-01 02:30:53.569221] W 
[marker-quota.c:2039:mq_inspect_directory_xattr] 0-teststatic-marker: 
cannot add a new contribution node
[2013-12-01 02:30:53.569328] W 
[marker-quota.c:2039:mq_inspect_directory_xattr] 0-teststatic-marker: 
cannot add a new contribution node
[2013-12-01 02:40:53.618593] W 
[marker-quota.c:2039:mq_inspect_directory_xattr] 0-teststatic-marker: 
cannot add a new contribution node
[2013-12-01 02:40:53.618686] W 
[marker-quota.c:2039:mq_inspect_directory_xattr] 0-teststatic-marker: 
cannot add a new contribution node
[2013-12-01 02:50:53.671236] W 
[marker-quota.c:2039:mq_inspect_directory_xattr] 0-teststatic-marker: 
cannot add a new contribution node






From:   gluster-users-request at gluster.org
To:     gluster-users at gluster.org
Date:   12/01/2013 05:58 AM
Subject:        Gluster-users Digest, Vol 68, Issue 1
Sent by:        gluster-users-bounces at gluster.org



Send Gluster-users mailing list submissions to
                 gluster-users at gluster.org

To subscribe or unsubscribe via the World Wide Web, visit
                 
http://supercolony.gluster.org/mailman/listinfo/gluster-users
or, via email, send a message with subject or body 'help' to
                 gluster-users-request at gluster.org

You can reach the person managing the list at
                 gluster-users-owner at gluster.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Gluster-users digest..."


Today's Topics:

   1. glusterfs 3.4 (Bernhard Glomm)
   2. Re: glusterfs 3.4 (Josh Boon)


----------------------------------------------------------------------

Message: 1
Date: Sat, 30 Nov 2013 13:13:26 +0000
From: "Bernhard Glomm" <bernhard.glomm at ecologic.eu>
To: gluster-users at gluster.org
Subject: [Gluster-users] glusterfs 3.4
Message-ID: <9cf432168fb022408c1b69f7f6360ed78beb5314 at ecologic.eu>
Content-Type: text/plain; charset="utf-8"

Hi all,

I just stumbled over a possible bug in glusterfs-3.4.1
Since I used the package from 
ppa:semiosis/ubuntu-glusterfs-3.4
for ubuntu (running 13.04 up to date)
I like to report here first / ask for confirmation.

I had glusterfs 3.3 installed and it worked fine.
I used it as the storage backend for the image files of my
kvm virtualized instances (two sided mirror/two kvm hosts
running four VM as a test environment)

I upgraded to 3.4 and all seemed okay on the first glance,
but live-migration failed with error:
"-incoming tcp:0.0.0.0:49153: Failed to bind socket: Address already in 
use"

reverting back to glusterfs 3.3
and the problem was gone

anybody knows about that prob?
couldn't find anything on the net about it yet.

best regards

Bernhard

-- 
sysadmin
www.ecologic.eu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <
http://supercolony.gluster.org/pipermail/gluster-users/attachments/20131130/aa252ec5/attachment-0001.html>
------------------------------

Message: 2
Date: Sat, 30 Nov 2013 16:27:14 -0600 (CST)
From: Josh Boon <gluster at joshboon.com>
To: Bernhard Glomm <bernhard.glomm at ecologic.eu>
Cc: gluster-users at gluster.org
Subject: Re: [Gluster-users] glusterfs 3.4
Message-ID: <1190686901.2696348.1385850434154.JavaMail.zimbra at 80ok.be>
Content-Type: text/plain; charset="utf-8"

Hey Bernhard, 

I'm running a very similar setup to you. What are your gluster options? 
What's the migration command you're using? Are you using gfapi or a fuse
mount? I think I've hit this error before but I'll need some info to jog
brain on how I fixed it. 

Best, 
Josh 

----- Original Message -----

From: "Bernhard Glomm" <bernhard.glomm at ecologic.eu> 
To: gluster-users at gluster.org 
Sent: Saturday, November 30, 2013 8:13:26 AM 
Subject: [Gluster-users] glusterfs 3.4 

Hi all, I just stumbled over a possible bug in glusterfs-3.4.1 Since I 
used the package from ppa:semiosis/ubuntu-glusterfs-3.4 for ubuntu 
(running 13.04 up to date) I like to report here first / ask for 
confirmation. I had glusterfs 3.3 installed and it worked fine. I used it 
as the storage backend for the image files of my kvm virtualized instances 
(two sided mirror/two kvm hosts running four VM as a test environment) I 
upgraded to 3.4 and all seemed okay on the first glance, but 
live-migration failed with error: "-incoming tcp:0.0.0.0:49153: Failed to 
bind socket: Address already in use" reverting back to glusterfs 3.3 and 
the problem was gone anybody knows about that prob? couldn't find anything 
on the net about it yet. best regards Bernhard -- sysadmin www.ecologic.eu 

_______________________________________________ 
Gluster-users mailing list 
Gluster-users at gluster.org 
http://supercolony.gluster.org/mailman/listinfo/gluster-users 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <
http://supercolony.gluster.org/pipermail/gluster-users/attachments/20131130/3f485609/attachment-0001.html>
------------------------------

_______________________________________________
Gluster-users mailing list
Gluster-users at gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-users

End of Gluster-users Digest, Vol 68, Issue 1
********************************************



**

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.
**
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://supercolony.gluster.org/pipermail/gluster-users/attachments/20131201/526f4046/attachment.html>

Khoi Mai

2013-Dec-01 16:01 UTC

head link

[Gluster-users] Repeative log messages, please help me interpret...

I also meant to show the PID of the volume



[root at node1 bricks]# fuser static-content.log-20131201
static-content.log-20131201:  6183
[root at node1 bricks]# ps -ef|grep 6183
root      6183     1 99 Nov20 ?        12-07:32:33 /usr/sbin/glusterfsd -s 
omhq1439 --volfile-id teststatic.omhq1439.static-content -p 
/var/lib/glusterd/vols/teststatic/run/omhq1439-static-content.pid -S 
/var/run/7aa439dc78b0d82ead0bce81f112d2e3.socket --brick-name 
/static/content -l /var/log/glusterfs/bricks/static-content.log 
--xlator-option *-posix.glusterd-uuid=ba566a39-6b8b-4a32-921a-188e4b00252e 
--brick-port 49153 --xlator-option teststatic-server.listen-port=49153


Kmai007





From:   Khoi Mai/UPC
To:     gluster-users at gluster.org
Date:   12/01/2013 09:56 AM
Subject:         Repeative log messages, please help me interpret...


Gluster community,


Ever since I've been running glusterfs3.4.1-3, log messages have gone out 
of control where I'd have 20G of space in /var and it gets filled up daily 
to 100% with the messages above.  Can someone please help me interpret the 
messages and suggest how I could resolve them?  My setup below is 2 node 
replicated volume.

Thank you,

kmai007

marker_lookup+0x2f8) [0x7fd954f7dfc8] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/features/marker.so(mq_req_xattr+0x3c) 
[0x7fd954f87f1c]))) 0-marker: invalid argument: loc->parent
[2013-12-01 02:22:28.529954] E 
[marker-quota-helper.c:229:mq_dict_set_contribution] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/debug/io-stats.so(io_stats_lookup+0x157)
[0x7fd954d682e7] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/features/marker.so(marker_lookup+0x2f8)
[0x7fd954f7dfc8] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/features/marker.so(mq_req_xattr+0x3c) 
[0x7fd954f87f1c]))) 0-marker: invalid argument: loc->parent
[2013-12-01 02:22:28.532913] E 
[marker-quota-helper.c:229:mq_dict_set_contribution] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/debug/io-stats.so(io_stats_lookup+0x157)
[0x7fd954d682e7] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/features/marker.so(marker_lookup+0x2f8)
[0x7fd954f7dfc8] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/features/marker.so(mq_req_xattr+0x3c) 
[0x7fd954f87f1c]))) 0-marker: invalid argument: loc->parent
[2013-12-01 02:22:28.534800] E 
[marker-quota-helper.c:229:mq_dict_set_contribution] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/debug/io-stats.so(io_stats_lookup+0x157)
[0x7fd954d682e7] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/features/marker.so(marker_lookup+0x2f8)
[0x7fd954f7dfc8] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/features/marker.so(mq_req_xattr+0x3c) 
[0x7fd954f87f1c]))) 0-marker: invalid argument: loc->parent
[2013-12-01 02:22:28.537790] E 
[marker-quota-helper.c:229:mq_dict_set_contribution] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/debug/io-stats.so(io_stats_lookup+0x157)
[0x7fd954d682e7] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/features/marker.so(marker_lookup+0x2f8)
[0x7fd954f7dfc8] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/features/marker.so(mq_req_xattr+0x3c) 
[0x7fd954f87f1c]))) 0-marker: invalid argument: loc->parent
[2013-12-01 02:22:28.540071] E 
[marker-quota-helper.c:229:mq_dict_set_contribution] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/debug/io-stats.so(io_stats_lookup+0x157)
[0x7fd954d682e7] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/features/marker.so(marker_lookup+0x2f8)
[0x7fd954f7dfc8] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/features/marker.so(mq_req_xattr+0x3c) 
[0x7fd954f87f1c]))) 0-marker: invalid argument: loc->parent
[2013-12-01 02:22:28.542266] E 
[marker-quota-helper.c:229:mq_dict_set_contribution] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/debug/io-stats.so(io_stats_lookup+0x157)
[0x7fd954d682e7] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/features/marker.so(marker_lookup+0x2f8)
[0x7fd954f7dfc8] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/features/marker.so(mq_req_xattr+0x3c) 
[0x7fd954f87f1c]))) 0-marker: invalid argument: loc->parent
[2013-12-01 02:22:28.544497] E 
[marker-quota-helper.c:229:mq_dict_set_contribution] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/debug/io-stats.so(io_stats_lookup+0x157)
[0x7fd954d682e7] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/features/marker.so(marker_lookup+0x2f8)
[0x7fd954f7dfc8] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/features/marker.so(mq_req_xattr+0x3c) 
[0x7fd954f87f1c]))) 0-marker: invalid argument: loc->parent
[2013-12-01 02:22:28.546424] E 
[marker-quota-helper.c:229:mq_dict_set_contribution] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/debug/io-stats.so(io_stats_lookup+0x157)
[0x7fd954d682e7] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/features/marker.so(marker_lookup+0x2f8)
[0x7fd954f7dfc8] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/features/marker.so(mq_req_xattr+0x3c) 
[0x7fd954f87f1c]))) 0-marker: invalid argument: loc->parent
[2013-12-01 02:22:28.549751] E 
[marker-quota-helper.c:229:mq_dict_set_contribution] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/debug/io-stats.so(io_stats_lookup+0x157)
[0x7fd954d682e7] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/features/marker.so(marker_lookup+0x2f8)
[0x7fd954f7dfc8] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/features/marker.so(mq_req_xattr+0x3c) 
[0x7fd954f87f1c]))) 0-marker: invalid argument: loc->parent
[2013-12-01 02:22:28.551996] E 
[marker-quota-helper.c:229:mq_dict_set_contribution] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/debug/io-stats.so(io_stats_lookup+0x157)
[0x7fd954d682e7] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/features/marker.so(marker_lookup+0x2f8)
[0x7fd954f7dfc8] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/features/marker.so(mq_req_xattr+0x3c) 
[0x7fd954f87f1c]))) 0-marker: invalid argument: loc->parent
[2013-12-01 02:22:28.554252] E 
[marker-quota-helper.c:229:mq_dict_set_contribution] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/debug/io-stats.so(io_stats_lookup+0x157)
[0x7fd954d682e7] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/features/marker.so(marker_lookup+0x2f8)
[0x7fd954f7dfc8] 
(-->/usr/lib64/glusterfs/3.4.1/xlator/features/marker.so(mq_req_xattr+0x3c) 
[0x7fd954f87f1c]))) 0-marker: invalid argument: loc->parent
[2013-12-01 02:30:53.569221] W 
[marker-quota.c:2039:mq_inspect_directory_xattr] 0-teststatic-marker: 
cannot add a new contribution node
[2013-12-01 02:30:53.569328] W 
[marker-quota.c:2039:mq_inspect_directory_xattr] 0-teststatic-marker: 
cannot add a new contribution node
[2013-12-01 02:40:53.618593] W 
[marker-quota.c:2039:mq_inspect_directory_xattr] 0-teststatic-marker: 
cannot add a new contribution node
[2013-12-01 02:40:53.618686] W 
[marker-quota.c:2039:mq_inspect_directory_xattr] 0-teststatic-marker: 
cannot add a new contribution node
[2013-12-01 02:50:53.671236] W 
[marker-quota.c:2039:mq_inspect_directory_xattr] 0-teststatic-marker: 
cannot add a new contribution node







From:   gluster-users-request at gluster.org
To:     gluster-users at gluster.org
Date:   12/01/2013 05:58 AM
Subject:        Gluster-users Digest, Vol 68, Issue 1
Sent by:        gluster-users-bounces at gluster.org



Send Gluster-users mailing list submissions to
                 gluster-users at gluster.org

To subscribe or unsubscribe via the World Wide Web, visit
                 
http://supercolony.gluster.org/mailman/listinfo/gluster-users
or, via email, send a message with subject or body 'help' to
                 gluster-users-request at gluster.org

You can reach the person managing the list at
                 gluster-users-owner at gluster.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Gluster-users digest..."


Today's Topics:

   1. glusterfs 3.4 (Bernhard Glomm)
   2. Re: glusterfs 3.4 (Josh Boon)


----------------------------------------------------------------------

Message: 1
Date: Sat, 30 Nov 2013 13:13:26 +0000
From: "Bernhard Glomm" <bernhard.glomm at ecologic.eu>
To: gluster-users at gluster.org
Subject: [Gluster-users] glusterfs 3.4
Message-ID: <9cf432168fb022408c1b69f7f6360ed78beb5314 at ecologic.eu>
Content-Type: text/plain; charset="utf-8"

Hi all,

I just stumbled over a possible bug in glusterfs-3.4.1
Since I used the package from 
ppa:semiosis/ubuntu-glusterfs-3.4
for ubuntu (running 13.04 up to date)
I like to report here first / ask for confirmation.

I had glusterfs 3.3 installed and it worked fine.
I used it as the storage backend for the image files of my
kvm virtualized instances (two sided mirror/two kvm hosts
running four VM as a test environment)

I upgraded to 3.4 and all seemed okay on the first glance,
but live-migration failed with error:
"-incoming tcp:0.0.0.0:49153: Failed to bind socket: Address already in 
use"

reverting back to glusterfs 3.3
and the problem was gone

anybody knows about that prob?
couldn't find anything on the net about it yet.

best regards

Bernhard

-- 
sysadmin
www.ecologic.eu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <
http://supercolony.gluster.org/pipermail/gluster-users/attachments/20131130/aa252ec5/attachment-0001.html>
------------------------------

Message: 2
Date: Sat, 30 Nov 2013 16:27:14 -0600 (CST)
From: Josh Boon <gluster at joshboon.com>
To: Bernhard Glomm <bernhard.glomm at ecologic.eu>
Cc: gluster-users at gluster.org
Subject: Re: [Gluster-users] glusterfs 3.4
Message-ID: <1190686901.2696348.1385850434154.JavaMail.zimbra at 80ok.be>
Content-Type: text/plain; charset="utf-8"

Hey Bernhard, 

I'm running a very similar setup to you. What are your gluster options? 
What's the migration command you're using? Are you using gfapi or a fuse
mount? I think I've hit this error before but I'll need some info to jog
brain on how I fixed it. 

Best, 
Josh 

----- Original Message -----

From: "Bernhard Glomm" <bernhard.glomm at ecologic.eu> 
To: gluster-users at gluster.org 
Sent: Saturday, November 30, 2013 8:13:26 AM 
Subject: [Gluster-users] glusterfs 3.4 

Hi all, I just stumbled over a possible bug in glusterfs-3.4.1 Since I 
used the package from ppa:semiosis/ubuntu-glusterfs-3.4 for ubuntu 
(running 13.04 up to date) I like to report here first / ask for 
confirmation. I had glusterfs 3.3 installed and it worked fine. I used it 
as the storage backend for the image files of my kvm virtualized instances 
(two sided mirror/two kvm hosts running four VM as a test environment) I 
upgraded to 3.4 and all seemed okay on the first glance, but 
live-migration failed with error: "-incoming tcp:0.0.0.0:49153: Failed to 
bind socket: Address already in use" reverting back to glusterfs 3.3 and 
the problem was gone anybody knows about that prob? couldn't find anything 
on the net about it yet. best regards Bernhard -- sysadmin www.ecologic.eu 

_______________________________________________ 
Gluster-users mailing list 
Gluster-users at gluster.org 
http://supercolony.gluster.org/mailman/listinfo/gluster-users 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <
http://supercolony.gluster.org/pipermail/gluster-users/attachments/20131130/3f485609/attachment-0001.html>
------------------------------

_______________________________________________
Gluster-users mailing list
Gluster-users at gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-users

End of Gluster-users Digest, Vol 68, Issue 1
********************************************



**

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.
**
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://supercolony.gluster.org/pipermail/gluster-users/attachments/20131201/19a9ba4a/attachment.html>

Gluster users - Dec 2013 - Repeative log messages, please help me interpret...

[Gluster-users] Repeative log messages, please help me interpret...

[Gluster-users] Repeative log messages, please help me interpret...