From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: Gareth Pye <gareth@cerberos.id.au>, Duncan <1i5t5.duncan@cox.net>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: utils version and convert crash
Date: Tue, 1 Dec 2015 15:30:14 -0500 [thread overview]
Message-ID: <565E0356.9030006@gmail.com> (raw)
In-Reply-To: <CA+WRLO_hx3u0wPy_GfguKmmXY4crxrRFx9TvuoLYh-Su0ju8ww@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1256 bytes --]
On 2015-12-01 15:12, Gareth Pye wrote:
> On Wed, Dec 2, 2015 at 2:14 AM, Duncan <1i5t5.duncan@cox.net> wrote:
>> So if you're running into the same problem gentoo's live-git build did,
>> it's likely because you're building the devel branch cloned from
>> kernel.org, which is no longer updated.
>
>
> Woah, kernel.org is making a log that looks like it's up to date but
> isn't that's awkward :(
>
> Building now from the github you mentioned.
>
> Also running a scrub, but I'm starting to suspect something else is
> responsible. It ran fine overnight but crashed in less than a minute
> after I logged back in on ssh this morning . . .
>
Hmm, the fact that it's intermittent is the most concerning part IMHO.
It means it's a lot harder to track down. If your hard drives aren't
any noisier than normal (most traditional hard disks get noticeably
noisier when they're failing), then I'd suggest running something like
memtest86+ for at least a full cycle with default options to verify if
your RAM is working correctly. Usually, when I see intermittent crashes
like this it's either a race condition in software somewhere, or bad
RAM, and it's a lot easier to test for bad RAM than it is to test for
race conditions.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3019 bytes --]
next prev parent reply other threads:[~2015-12-01 20:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-01 12:38 utils version and convert crash Gareth Pye
2015-12-01 12:57 ` Gareth Pye
2015-12-01 14:46 ` Duncan
2015-12-01 15:16 ` Austin S Hemmelgarn
2015-12-01 15:14 ` Duncan
2015-12-01 20:12 ` Gareth Pye
2015-12-01 20:30 ` Austin S Hemmelgarn [this message]
2015-12-01 22:22 ` Gareth Pye
2015-12-02 7:07 ` Gareth Pye
2015-12-02 10:01 ` Duncan
2015-12-02 12:07 ` Gareth Pye
2015-12-02 12:25 ` Austin S Hemmelgarn
2015-12-02 13:45 ` Duncan
2015-12-02 14:32 ` Austin S Hemmelgarn
2015-12-02 22:14 ` Gareth Pye
2016-02-28 10:23 ` Gareth Pye
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=565E0356.9030006@gmail.com \
--to=ahferroin7@gmail.com \
--cc=1i5t5.duncan@cox.net \
--cc=gareth@cerberos.id.au \
--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.