Dne 17.8.2015 v 13:30 Miloš Kozák
napsal(a):
Dne 17.8.2015 v 10:07 Ravishankar N napsal(a):
On 08/17/2015 12:42 PM, Miloš Kozák wrote:
I assumed that those files are different
because of different file size.
I then reckon the writes are not successful on the 2nd node. The
brick log should give some clue. You can also check the fuse
mount log for errors.
Yes this seems like it.. I am enclosing node2 brick logs
Ok, so my MD5s are:
[root@nodef01i fs]# md5sum *
6bc6e89a9cb46a4098db300ff6d95b46
f1607f25aa52f4fb6f98f20ef0f3f9d7
0989d12cc875387827ebbbdc67503f2b
3706a2cb0bb27ba5787b3c12388f4ebb
[root@nodef01i fs]# md5sum *
0989d12cc875387827ebbbdc67503f2b
3706a2cb0bb27ba5787b3c12388f4ebb
md5sum: 6bc6e89a9cb46a4098db300ff6d95b46: Adresář nebo soubor
neexistuje (File or folder does not exist)
The md5sum was run on the back-end bricks right? - In which case
the ENOENT error seems to indicate a corrupt file system.
(`dmesg` might show something).
Yes, on the back-end filesystems.. Dmesg is clear.
I find strange that I get ENOENT, but glusters seems everything is
OK...
When I had split-brain problem, I had the same type of error when I
wanted to access the file which was split-brained... however, I am
not sure if it was at the brick level or volume level..
Dne 17.8.2015 v 08:40 Ravishankar N napsal(a):
On 08/17/2015 11:58 AM, Miloš Kozák wrote:
Mounted by fuse.
I would not say written to only one node because both
nodes contain something, but I am quite suspicious about
files on the node2.
Not sure I follow. Is there a mismatch of the file's
contents on both nodes? You could do an md5sum check.
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users
|
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users
