On Jul 27, 2013, at 10:05 PM, Jérôme Poulin wrote:
> On Sat, Jul 27, 2013 at 1:06 PM, Vyacheslav Dubeyko <slava@xxxxxxxxxxx> wrote:
>> I tried to reproduce the issue but I haven't success in it.
>> Could you describe the reproducing path in more details?
>>
>
> Since I have a reproducible path, here is how I did:
> 1. init S to get to single user mode.
> 2. sysrq+E to make sure only my shell is running
> 3. start network-manager to get my wifi connection up
> 4. login as root and launch "screen"
> 5. cd /boot/log/nilfs which is a ext3 mount point and can log when NILFS dies.
> 6. lscp | xz -9e > lscp.txt.xz
> 7. mount my snapshot using mount -o cp=3360839,ro /dev/vgUbuntu/root /mnt/nilfs
> 8. start a screen to dump /proc/kmsg to text file since rsyslog is killed
> 9. start a screen and launch strace -f -o find-cat.log -t find
> /mnt/nilfs -type f -exec cat {} > /dev/null \;
> 10. start a screen and launch strace -f -o apt-get.log -t apt-get update
> 11. launch the last command again as it did not crash the first time
> 12. apt-get crashes
> 13. ps aux > ps-aux-crashed.log
> 13. sysrq+W
> 14. sysrq+E wait for everything to terminate
> 15. sysrq+SUSB
>
I have reproduced the issue successfully. So, I can begin to investigate it.
Thank you for efforts in the issue reproducing and detailed information
about the issue.
With the bets regards,
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
