From: Marc MERLIN <marc@merlins.org>
To: Omar Sandoval <osandov@osandov.com>
Cc: linux-btrfs@vger.kernel.org, pwnall@chromium.org
Subject: Re: Leveldb in google-chrome incompatible with btrfs?
Date: Thu, 6 Jul 2017 16:59:39 -0700 [thread overview]
Message-ID: <20170706235939.GJ30689@merlins.org> (raw)
In-Reply-To: <20170706234451.GB22242@vader.DHCP.thefacebook.com>
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/
next prev parent reply other threads:[~2017-07-06 23:59 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 [this message]
2017-07-07 5:46 ` Omar Sandoval
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=20170706235939.GJ30689@merlins.org \
--to=marc@merlins.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=osandov@osandov.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.