As was pointed out to me by Andy5_ on the IRC channel, qemu outputs the
glusterfs log on stdout:
https://github.com/qemu/qemu/blob/stable-1.7/block/gluster.c#L211
On 04/21/2014 09:51 AM, Paul Penev wrote:
I sent the brick logs earlier. But I'm not able to produce logs from
events in KVM. I can't find any logging or debugging interface. It is
somewhat weird.
Paul
2014-04-21 18:30 GMT+02:00 Joe Julian <joe@xxxxxxxxxxxxxxxx>:
I don't expect much from the bricks either, but in combination with the
client log they might tell us something.
On April 21, 2014 9:21:56 AM PDT, Paul Penev <ppquant@xxxxxxxxx> wrote:
Joe,
it will take some time for redo the logs (I'm doing them now).
While waiting for the heal to complete I did some research on the
version history of qemu.
There's a patch made two months ago that intrigues me:
https://github.com/qemu/qemu/commit/adccfbcd6020e928db93b2b4faf0dbd05ffbe016
Also the changelog
https://github.com/qemu/qemu/commits/master/block/gluster.c seems to
support some work done recently in gluster.c
keep tuned for the logs from the bricks (but I don't expect much there).
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-users
