Vyacheslav Dubeyko skrev 2013-08-30 07:58:
On Mon, 2013-08-26 at 20:37 +0200, Anton Eliasson wrote:
You're welcome. And thank you for your thorough instructions. It's been
very informative and worthwhile for me to patch and build a kernel with
custom options. Let me know if you need more experiments run on the
damaged filesystem. Otherwise I'll delete the stored disk images in a
month or two.
As I remember, you reproduced the issue by means of starting of two
virtual machines. I think that I will try to reproduce the issue by this
way. But I am investigating the another issue currently and,
unfortunately, I haven't opportunities for investigating this issue in
parallel.
I don't fully confident that it is possible to do it. But, does it
possible to collect strace output of virtual machines starting for the
case of reproduced issue? What do you think? You have shared kernel log
for the reproduced issue case, currently. But strace output can give
interesting details from the user-space point of view.
Thanks,
Vyacheslav Dubeyko.
I spent about an hour trying to reproduce this today. I built Linux
3.10.10 using your patches from June. The patch command reported some
offsets and fuzz so it seems that the nilfs driver has changed since the
last kernel version. I don't know if the updates affect this bug. With
this new cusom kernel, everything I/O related ran very slowly. The nilfs
garbage collector used 100 % CPU constantly. Killing it sped things up a
little.
I started and stopped the virtual machines a few times, with reboots in
between. Eventually the system tried to touch some corrupted parts of
the virtual machine image and /home remounted read-only. At that point I
gave up. I doubt the strace output will help you but I uploaded it here
[1] anyway. VMware Workstation is a complex application that consists of
many executables. Some are run directly by the user, some as system
services and some as kernel modules. Picking the right place to stick
the multimeter probe is probably difficult.
Unfortunately I forgot to install syslog-ng today and my instance of
systemd is not configured to log verbosely enough to capture the kernel
debug output. So no kernel.log for today. This is all starting to feel
like a waste of time for me as I don't even use nilfs on any of my
machines anymore. I'm going to withdraw my offer to debug these issues
any further. Sorry. I hope you have gathered enough information to solve
them and I wish you the best of luck.
[1]: http://antoneliasson.se/publicdump/vmware-strace.log.gz
--
Best Regards,
Anton Eliasson
--
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
