On Fri, 10 Jun 2016, Chris Murphy wrote: > > Are those issues something which was fixed since 4.6.0-rc4+ or I should > > be on look out for them to come back? What other information should I > > provide if I run into them again to help you troubleshoot/fix it?
> > P.S. Please CC me the replies > 4.6.2 is current and it's a lot easier to just use that and see if it > still happens than for someone to track down whether it's been fixed > since a six week old RC. Dear Chris, Thank you for the reply! Now running v4.7-rc2-300-g3d0f0b6 The thing is that this issue doesn't happen right away, and it takes a while for it to develop, and seems to be only after an intensive load. So the version I run will always be "X weeks old" if I just keep hopping the recent release of master, and it would be an indefinite goose chase if left un-analyzed. That is why I would still appreciate an advice on what specifics to report/attempt if such crash happens next time, or may be if someone is having an idea of what could have lead to this crash to start with. -- Yaroslav O. Halchenko, Ph.D. http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org Research Scientist, Psychological and Brain Sciences Dept. Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
