From: Marc MERLIN <marc@merlins.org>
To: linux-btrfs@vger.kernel.org
Subject: Unclean shutdowns cause google-chrome profile to be corrupted in various ways
Date: Fri, 22 Aug 2014 08:50:40 -0700 [thread overview]
Message-ID: <20140822155040.GU3875@merlins.org> (raw)
Someone just told me yesterday they had the same problem, so I filed a
bug:
https://bugzilla.kernel.org/show_bug.cgi?id=83041
Fairly often (over 20 times for me so far with various kernel versions),
when I reboot after a crash, my google-chrome profile is damaged in one
of 2 ways:
1) open tabs don't reopen
2) google-chrome says that my profile is corrupted.
In both cases rsyncing ~/.config/google-chrome from the last hourly
snapshot has fixed the problem every time.
Given that, I would say that google-chrome does not have a bug of half
unclean states since the state present in a snapshot has always worked
for me, but that's anecdotal, not proof.
But if my kernel hangs due to a bug that isn't btrfs' fault and I need
to power off and back on, after reboot my google-chrome profile is
almost always broken in some way.
This with a samsung evo 840 SSD which I believe does reasonable enough
things on power shutdowns, although I can't prove that.
File formats are some kind of raw data and sqlite 3.x
~/.config/google-chrome-beta/Profile 1:
Last Session: data
Last Tabs: data
Login Data: SQLite 3.x database
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/ | PGP 1024R/763BE901
next reply other threads:[~2014-08-22 16:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-22 15:50 Marc MERLIN [this message]
2014-08-22 17:32 ` Unclean shutdowns cause google-chrome profile to be corrupted in various ways Eric Sandeen
2014-08-22 18:46 ` Marc MERLIN
2014-08-22 18:17 ` Duncan
2014-08-22 18:49 ` Marc MERLIN
2014-08-23 2:52 ` Duncan
2014-08-23 3:10 ` Marc MERLIN
2014-08-23 5:45 ` Naohiro Aota
2014-08-23 12:32 ` Marc MERLIN
2014-08-23 13:09 ` Holger Hoffstätte
2014-08-23 5:56 ` Duncan
2014-08-23 12:34 ` Marc MERLIN
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=20140822155040.GU3875@merlins.org \
--to=marc@merlins.org \
--cc=linux-btrfs@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).