Kaperstone / mogilefs

Automatically exported from code.google.com/p/mogilefs
0 stars 0 forks source link

Replication to Storage Node Causes 0 byte files #63

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Normal replication to a storage node within a pool was not working properly.
2. For a period of time, files which were supposed to be replicated to our 
Storage pool, were only successfully written to 2 of the 3 storage nodes.
3. One of the storage nodes had the file there (with correct name) but with a 0 
bytes in size.
4. Exact steps to reproduce the problem are unknown, a restart of the server 
appeared to have fixed the issue.

What is the expected output? What do you see instead?
We expected to see 3 replicas in our storage pool although mogstats showed the 
correct number of files replicated among all of the hosts.

What version of the product are you using? On what operating system?
CentOS v6.2
Client - v1.15
Server - v2.57

Please provide any additional information below.
Again, the unusual thing is that a server reboot fixed the issue.  We are still 
parsing through logs to understand exact root cause but any insight is greatly 
appreciated.

Original issue reported on code.google.com by wiktor.m...@gmail.com on 10 May 2012 at 4:36

GoogleCodeExporter commented 8 years ago
I feel like we troubledshot this in IRC.

For posterity; it was most likely a filesystem glitch, not related to mogilefs 
at all.

Original comment by dorma...@rydia.net on 20 Jun 2012 at 12:46