linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc MERLIN <marc@merlins.org>
To: Duncan <1i5t5.duncan@cox.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Unclean shutdowns cause google-chrome profile to be corrupted in various ways
Date: Fri, 22 Aug 2014 11:49:19 -0700	[thread overview]
Message-ID: <20140822184919.GE3875@merlins.org> (raw)
In-Reply-To: <pan$a7366$366442ed$60aa89a1$c636b8e3@cox.net>

On Fri, Aug 22, 2014 at 06:17:38PM +0000, Duncan wrote:
> Marc MERLIN posted on Fri, 22 Aug 2014 08:50:40 -0700 as excerpted:
> 
> > 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.
> 
> I've had a similar issue with firefox, tho I've narrowed it down to a 

Ok, so so far we've had:
1) gogole-chrome
2) firefox
3) mysql

and 3 different people reporting this at least.

Google-chrome is complicated because it has many state files and I
haven't narrowed down which one got corrupted.
In your firefox example, did you find what corruption you got in that
file, or was it just truncated?

For mysql, I got:
InnoDB: Page directory corruption: infimum not pointed to
140708 11:53:58  InnoDB: Page dump in ascii and hex (16384 bytes):
 len 16384; hex 00000000(16KB of 0's).

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

  reply	other threads:[~2014-08-22 18:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-22 15:50 Unclean shutdowns cause google-chrome profile to be corrupted in various ways Marc MERLIN
2014-08-22 17:32 ` Eric Sandeen
2014-08-22 18:46   ` Marc MERLIN
2014-08-22 18:17 ` Duncan
2014-08-22 18:49   ` Marc MERLIN [this message]
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=20140822184919.GE3875@merlins.org \
    --to=marc@merlins.org \
    --cc=1i5t5.duncan@cox.net \
    --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).