Hi Michael, On Nov 19, 2013, at 8:53 PM, Michael Conrad wrote:
Sorry, I were in business trip and I haven't access to my e-mail. > Hi, its me again. > > I've upgraded my systems to 3.2.52 (direct from kernel.org, no gentoo patches > any more), and haven't had a reboot since. However, I just ran into a new > problem where a power glitch caused an external USB drive to reset, and the > nilfs kernel module didn't handle it well. The mount point is frozen, and > any process that accesses it freezes and can't be killed even with kill -9. > It was mounted with default mount options. > > I've attached the complete kernel log from the time the USB device > disconnected. It ends with "Kernel Bug, invalid opcode 0000" in > nilfs_btnode_prepare_change_key. > > The system is still running and doing fine other than this, and "umount -l" > worked to remove it from the filesystem so that more processes don't get > stuck. However, this project I'm working on has used up a lot more time than > I expected, and I'll have to try a different filesystem if I can't get it > working reliably, soon :-( Would you like any additional debugging info? > Thank you for the issue report. So, I need in reproducing path for investigating of the issue. Can you reproduce the issue stably on your side? Could you describe reproducing path for me? What workload do you have during power glitch and USB drive reset? Could you describe your environment in more details? 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
