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 20:10:55 -0700 [thread overview]
Message-ID: <20140823031055.GH3875@merlins.org> (raw)
In-Reply-To: <pan$644c4$e5e83b2d$34cd9e4d$75795b7@cox.net>
On Sat, Aug 23, 2014 at 02:52:16AM +0000, Duncan wrote:
> > 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).
>
> Is that on ssd or spinning rust, and if ssd, do you run with trim/discard
> and/or have you filled the device yet if not (since mkfs.btrfs trims the
> device as part of the process)? I'm wondering if that's 4 4 KiB btrfs
> data blocks of trimmed and unwritten SSD?
It's on SSD, I do have trim/discard, I never filled the device.
But I could totally remove trim and see what happens. I'll do that.
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 prev parent reply other threads:[~2014-08-23 3:10 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
2014-08-23 2:52 ` Duncan
2014-08-23 3:10 ` Marc MERLIN [this message]
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=20140823031055.GH3875@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 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.