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 14:24:22 -0700 [thread overview]
Message-ID: <20170706212422.GH30689@merlins.org> (raw)
In-Reply-To: <20170706211320.GA12206@vader.DHCP.thefacebook.com>
On Thu, Jul 06, 2017 at 02:13:20PM -0700, Omar Sandoval wrote:
> On Thu, Jul 06, 2017 at 08:00:46AM -0700, Marc MERLIN wrote:
> > I don't know who else uses google-chrome here, but for me, for as long as
> > I've used btrfs (3+ years now), I've had no end of troubles recovering from
> > a linux crash, and google-chrome has had problems recovering my tabs and
> > usually cmoplains about plenty of problems, some are corruption looking.
>
> I've also had issues with chrome and Btrfs, not just you.
>
> [snip]
>
> > Does anyone know if it's leveldb relying on non POSIX semantics that just
> > happen to work out on ext4, or if btrfs COW and atomicity doesn't quite
> > handle multi file updates in a way that is expected by a spec, or by
> > application developers?
>
> A quick google search turned this up: https://github.com/google/leveldb/issues/195.
> Unless anything has changed since that issue was last updated, it does
> sound like LevelDB is making some unsafe assumptions. I'll take a look.
Thanks Omar, this very much looks related indeed.
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 21:24 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 [this message]
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
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=20170706212422.GH30689@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.