On Sat, 23 Aug 2014 05:32:49 -0700, Marc MERLIN wrote:
> [snip]
> Thanks for that data point, so that rules out discard and SSDs.
>
> Given that, it sounds like btrfs may still have a bug where everything
> does not get to disk in the right order before the system stops.
A popular candidate for
On Sat, Aug 23, 2014 at 05:56:28AM +, Duncan wrote:
> Of course that begs the question of whether it was a normal COW file or
> if you had it NOCOW. Setting it NOCOW (of course doing the correct set
I had it at the default of COW, both chrome and mysql.
Marc
--
"A mouse is a device used t
On Sat, Aug 23, 2014 at 02:45:25PM +0900, Naohiro Aota wrote:
> On Sat, Aug 23, 2014 at 12:10 PM, Marc MERLIN wrote:
> > On Sat, Aug 23, 2014 at 02:52:16AM +, Duncan wrote:
> >> > For mysql, I got:
> >> > InnoDB: Page directory corruption:
> >> > infimum not pointed to 140708 11:53:58
> >> > I
Marc MERLIN posted on Fri, 22 Aug 2014 20:10:55 -0700 as excerpted:
> On Sat, Aug 23, 2014 at 02:52:16AM +, 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 1
On Sat, Aug 23, 2014 at 12:10 PM, Marc MERLIN wrote:
> On Sat, Aug 23, 2014 at 02:52:16AM +, 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 0
On Sat, Aug 23, 2014 at 02:52:16AM +, 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 (16KB of 0's).
>
> Is that on ssd or spinning rust, and
Marc MERLIN posted on Fri, 22 Aug 2014 11:49:19 -0700 as excerpted:
> On Fri, Aug 22, 2014 at 06:17:38PM +, 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
On Fri, Aug 22, 2014 at 06:17:38PM +, 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:
>
On Fri, Aug 22, 2014 at 12:32:27PM -0500, Eric Sandeen wrote:
> On 8/22/14, 10:50 AM, Marc MERLIN wrote:
>
> > 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.
>
> Gi
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
On 8/22/14, 10:50 AM, Marc MERLIN wrote:
> 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.
Given my experiences with userspace in general, I'd lay money on
google-chrome
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
12 matches
Mail list logo
