A ceph user observed a incorrect i_size on btrfs. The pattern looks like this: - some writes at low file offsets - a write to 4185600 len 8704 (i_size should be 4MB) - more writes to low offsets - a write to 4181504 len 4096 (abutts the write above) - a bit of time goes by... - stat returns 4186112 (4MB - 8192) - that's a fwe bytes to the right of the top write above. There are some logs showing the full read/write activity to the file at http://tracker.newdream.net/attachments/658/object_log.txt on issue http://tracker.newdream.net/issues/3810 The kernel was 3.7.0-030700-generic (and probably also observed on 3.7.1). Is this a known bug? Thanks! sage -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
