Hi Andreas, On Jan 2, 2014, at 5:48 PM, Andreas Rohner wrote: > There is a bug in the function nilfs_segctor_collect, which results in > active data being written to a segment, that is marked as clean. It is > possible, that this segment is selected for a later segment > construction, whereby the old data is overwritten. > Thank you for your patch. But, currently, I doubt that your patch is correct. What version of the kernel did you used during the issue reproducing? Do you have the patch [1] in your kernel? The description of the issue looks like the problem that it was fixed in my patch. So, do you confident that you reproduce the issue with presence of patch [1] in your kernel? Could you check and confirm it? Of course, you can discover some new issue. But, currently, I can't understand relation between the error message from nilfs_sufile_do_cancel_free() and next messages from nilfs_bmap_last_key() from your description. So, I need to think over your description more deeply and I need in confirmation that you reproduce the issue with presence of patch [1] in your kernel. Thanks, Vyacheslav Dubeyko. [1] http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/3082 -- To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
