On Thu, Jul 06, 2017 at 04:59:39PM -0700, Marc MERLIN wrote: > 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.
Okay, this makes 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. Sounds good. > But you said you've also seen issues with google-chrome profile and btrfs. > What did you experience? I never debugged it, but I had to blow away the profile a couple of times. Then there's this weird one which looks like a Btrfs bug: ┌[osandov@vader ~/.config] └$ ls -al google-chrome-busted/** ls: cannot access 'google-chrome-busted/Local State': No such file or directory google-chrome-busted/Default: ls: cannot access 'google-chrome-busted/Default/Preferences': No such file or directory ls: cannot access 'google-chrome-busted/Default/.com.google.Chrome.VfAUNx': No such file or directory total 0 drwx------ 1 osandov users 12 Feb 7 16:50 . drwx------ 1 osandov users 14 Feb 7 16:50 .. -????????? ? ? ? ? ? .com.google.Chrome.VfAUNx -????????? ? ? ? ? ? Preferences -- 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
