Hello Vijay
There's nothing after that string in my log file. After crashing, log
file stopped printing output, and i had to remount it then. So the log
file looks like this:
/package-string: glusterfs 3.2.5
/lib64/libc.so.6[0x3cf0c32900]
---------
[2012-06-27 23:02:43.446042] W [write-behind.c:3023:init]
0-cdt_store-write-behind: disabling write-behind for first 0 bytes
Given volfile:
+------------------------------------------------------------------------------+
1: volume cdt_store-client-0
2: type protocol/client
3: option remote-host Gnode1
4: option remote-subvolume /mnt/store
5: option transport-type tcp
6: end-volume
7:
8: volume cdt_store-client-1
9: type protocol/client
10: option remote-host Gnode2
11: option remote-subvolume /mnt/store2
12: option transport-type tcp
13: end-volume
14:
15: volume cdt_store-dht
16: type cluster/distribute
17: option min-free-disk 5
18: subvolumes cdt_store-client-0 cdt_store-client-1
19: end-volume
20:
21: volume cdt_store-write-behind
22: type performance/write-behind
23: option cache-size 4MB
24: subvolumes cdt_store-dht
25: end-volume
26:
27: volume cdt_store-read-ahead
28: type performance/read-ahead
29: subvolumes cdt_store-write-behind
30: end-volume
31:
32: volume cdt_store-io-cache
33: type performance/io-cache
34: option cache-size 512MB
35: subvolumes cdt_store-read-ahead
36: end-volume/
Many thanks
On 6/30/2012 10:16 AM, Vijay Bellur wrote:
On 06/29/2012 09:29 PM, tungdam wrote:
Hello Vijay
You mean the core dump file ? It is pretty big, i think, it's about > 1G
after gzip-ed.
Is that what you need ? ( I need to make sure that i'm not going to send
you the wrong - and big - info )
No, I would need the next 15-20 lines after a reference to
"package-string: glusterfs 3.2.5" in the log file of the client where
the crash was seen.
Regards,
Vijay
_______________________________________________
Gluster-users mailing list
[email protected]
http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
