Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Omar Sandoval <osandov@osandov.com>
To: Marc MERLIN <marc@merlins.org>
Cc: linux-btrfs@vger.kernel.org, pwnall@chromium.org
Subject: Re: Leveldb in google-chrome incompatible with btrfs?
Date: Thu, 6 Jul 2017 22:46:08 -0700	[thread overview]
Message-ID: <20170707054608.GA28035@vader> (raw)
In-Reply-To: <20170706235939.GJ30689@merlins.org>

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

  reply	other threads:[~2017-07-07  5:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-06 15:00 Leveldb in google-chrome incompatible with btrfs? Marc MERLIN
2017-07-06 21:13 ` Omar Sandoval
2017-07-06 21:24   ` Marc MERLIN
2017-07-06 23:01     ` Omar Sandoval
2017-07-06 23:31       ` Marc MERLIN
2017-07-06 23:44         ` Omar Sandoval
2017-07-06 23:59           ` Marc MERLIN
2017-07-07  5:46             ` Omar Sandoval [this message]
2017-07-07 15:05               ` Cerem Cem ASLAN
2017-07-07 16:50               ` Marc MERLIN
2017-07-12  8:14                 ` Cerem Cem ASLAN

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170707054608.GA28035@vader \
    --to=osandov@osandov.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=marc@merlins.org \
    --cc=pwnall@chromium.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox