On Sun, Nov 25, 2012 at 12:45 PM, Nathan Howell <nathan.d.howell@xxxxxxxxx> wrote: > So when trawling through the filesystem doing checksum validation > these popped up on the files that are filled with null bytes: > https://gist.github.com/186ad4c5df816d44f909 > > Is there any way to fsck today? Looks like feature #86 > http://tracker.newdream.net/issues/86 isn't implemented yet. Yeah, unfortunately there isn't — fsck is one of those things that we want to do as we prepare CephFS for production use, but we're only now starting to move back in that direction. The error printouts you're seeing indicate that...actually, I don't know what they mean in this context. Hrm. In any case, Zheng Yan contributed some patches that could impact a number of these issues, but I still don't see how the NULL bytes could enter into it from our end. If you can afford the disk space required to turn on "debug osd = 10" on the OSDs, and "debug mds = 10" on the MDS, that might give us a clue about what's going on, if we manage to grab the logs that overlap with the bad event (or at least the detection of it). You'll certainly want to enable log rotation, though — that will generate some very large logs. Sorry for the slow turnaround time on this, our attention is being pulled in a lot of directions besides CephFS and this is going to be a hard one. -Greg -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
