All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Murphy <lists@colorremedies.com>
To: Duncan <1i5t5.duncan@cox.net>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Bad hard drive - checksum verify failure forces readonly mount
Date: Thu, 23 Jun 2016 23:34:49 -0600	[thread overview]
Message-ID: <CAJCQCtQAXydm65n1P_YNF2r5EJmPYk6a2Q+x38zGzpLsagCgyg@mail.gmail.com> (raw)
In-Reply-To: <pan$4aafc$8178c223$638252a3$717a5f23@cox.net>

On Thu, Jun 23, 2016 at 10:56 PM, Duncan <1i5t5.duncan@cox.net> wrote:
> Chris Murphy posted on Thu, 23 Jun 2016 18:54:28 -0600 as excerpted:
>
>> From the pasted kernel messages:
>>
>>> Linux version 3.18.34-std473-amd64 (root@rl-sysrcd-p11) (gcc version
>>> 4.8.5 (Gentoo 4.8.5 p1.3, pie-0.6.2) ) #2 SMP Tue May 24 20:34:19 UTC
>>> 2016
>>
>>
>> 3.18.34 is ancient. Find something newer and try to remount normally.
>> And then also with recovery if necessary (don't use ro, see if it'll
>> mount rw and fix itself). And if not, then try btrfs check with a newer
>> version of btrfs-progs, I can't tell from the pasted output what version
>> you're using but since the kernel is so old, decent chance the btrfsck
>> is old also.
>
> ...  So I guess that means we're back to supporting only the latest two
> LTS kernel series, those being 4.1 and 4.4 at this time.  I had hoped
> that btrfs was stabilizing enough, and 3.18 was trouble-free enough btrfs-
> wise, that we could expand that to three LTS series now, as the
> indications were we might when 4.4 was still new.  But it seems that
> while we did support it a bit longer, say 2.5 LTS series, that couldn't
> continue until the /next/ LTS came out.
>
> Oh, well, it /was/ a bit of a stretch...

Yeah looks like 3.18.35 even has some backports, and it's not that old
but I have no idea if the problem in this case if fixed by something
newer.

I'd say 50/50 shot at a new kernel doing better, but for the sure the
btrfs-progs has a better chance because btrfsck has had lots of
improvements since 3.18. It's just too easy to dd a Fedora 24 live
image to a USB stick, which has kernel 4.5.5 and btrfs-progs 4.5.2 and
give it a shot. And if that doesn't work, then btrfs-image time so
hopefully devs can see if it's possible to improve btrfsck. But at
that point it also means blowing away this fs :-\ but at least it's ro
mountable so anything important can be copied off normally.

-- 
Chris Murphy

  reply	other threads:[~2016-06-24  5:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-23 20:30 Bad hard drive - checksum verify failure forces readonly mount Vasco Almeida
2016-06-24  0:54 ` Chris Murphy
2016-06-24  4:56   ` Duncan
2016-06-24  5:34     ` Chris Murphy [this message]
     [not found]   ` <5356822.A3RRKHDHNy@linux-omuo>
2016-06-24 16:47     ` Chris Murphy
2016-06-25  0:06       ` Vasco Almeida
2016-06-25 13:20         ` Chris Murphy
2016-06-25 20:10           ` Vasco Almeida
2016-06-25 20:54             ` Chris Murphy
2016-06-26 13:05               ` Vasco Almeida
2016-06-26 19:54                 ` Chris Murphy
2016-06-27  6:30                   ` Vasco Almeida
2016-06-27 16:49                     ` Chris Murphy
2016-07-05 17:43                       ` Vasco Almeida

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=CAJCQCtQAXydm65n1P_YNF2r5EJmPYk6a2Q+x38zGzpLsagCgyg@mail.gmail.com \
    --to=lists@colorremedies.com \
    --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.