Hi, On Thu, 2012-12-20 at 19:02 +0800, 张 磊 wrote: > Yes, I mounted NILFS2 as read-write. It's remounted as read-only by kernel > when filesystem found the bad btree node. > > That's the full backtrace. I will keep on testing, and report more infomation > once I found. >
I am trying to reproduce the issue but currently without any success. I have a presupposition that it can be a synchronization issue between GC and main driver logic but I haven't any evidence of it yet. Probably, I can't reproduce some environment's peculiarities. So, I think that I need to understand more deeply a workload in that the issue had occurred. As I remember, you talked about several MySQL databases and so on. Could you describe in more details about what applications and how to work before issue occurrence? Thanks, Vyacheslav Dubeyko. -- To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
