On Tue, 2013-12-10 at 08:47 -0800, Jon Watte wrote: > Thanks for your suggestions. I have no idea about how to reproduce the > issue -- this is a light-to-medium-use desktop system. I think that it is important to understand a nature of workload on your system. Maybe do you use some application frequently or process some data mainly on this system? Is it possible to distinguish frequent and repeatable workload? > I took an image of that volume and can mount it on an older kernel if > I need to copy out any files, although all of the important stuff was > in git or dropbox off-site, so no data really lost. > Is there anything I can do to this volume that would give you more > information about what the cause might be (i e, whether the cause is > patched or not)? > Some debug utility that will create a dump of some sort that will > help? Else I will probably just wipe that image and recover the 30G of > space. > I think that I have a request to you. It is very important to understand that my patch fixes the issue really. So, please, take attention to the situation on newly created NILFS2 volume under Linux kernel with the patch. If you will encounter the issue again then it means that the reason of the issue doesn't be fixed. I believe that I had fixed the issue's reason. But there is probability to have another reason of such error messages. Thanks, Vyacheslav Dubeyko. -- 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
