On Thu, Jul 06, 2017 at 04:44:51PM -0700, Omar Sandoval wrote:
> In the bug report, you commented that CURRENT contained MANIFEST-010814,
> is that indeed the case or was it actually something newer? If it was
> the newer one, then it's still tricky how we'd end up that way but not
> as outlandish.
You are correct, my bad.
At this point, I'm going to have to assume that something bad happened with
rsync when I rsync'ed an old profile over the one that caused chrome to fail
to restart.
Especially because CURRENT was dated Oct 4th, which does not make sense.
Now that I know what to look for, I'll have a much closer look next time
this happens, with the understanding that it would be a while if I've
successfully fixed the reason why my laptop was crashing too often.
But you said you've also seen issues with google-chrome profile and btrfs.
What did you experience?
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
