All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Pernegger <pernegger@gmail.com>
To: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>,
	Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: first it froze, now the (btrfs) root fs won't mount ...
Date: Thu, 24 Oct 2019 12:41:37 +0200	[thread overview]
Message-ID: <CAKbQEqGoiGbV+Q=LVfSbKLxYeQ5XmLFMMBdq_yxSR7XE3SwsmA@mail.gmail.com> (raw)
In-Reply-To: <0d6683ee-4a2c-f2ab-857b-c7cd44442dce@gmail.com>

I must admit, this discussion is going (technical) places I don't know
anything about, and much as I enjoy learning things, I'd rather not
waste your time (go make btrfs better! :-p). When all is said and done
I'm just a user. I still don't understand how (barring creatively
defective hardware, which is of course always in the cards) a crash
that looked comparatively benign could lead to an fs that's not only
unmountable but unfixable; how metadata that's effectively a single
point of failure could not have backup copies designed in that are
neither stale nor left to the elements, seems awfully fragile -- but I
can accept it. Repair is out.

Recovery it is, then. I'd like to try and build this rescue branch of
yours. Does it have to be the whole thing, or can btrfs alone be built
against the headers of the distro kernel somehow, or can the distro
kernel source be patched with the rescue stuff? Git wasn't a thing the
last time I played with kernels, a shove in the right direction would
be appreciated.

Relapse prevention. "Update everything and pray it's either been fixed
or at least isn't triggered any more" isn't all to
confidence-inspiring. Desktop computers running remotely current
software will crash from time to time, after all, if not amdgpu then
something else. At which point we're back at "a crash shouldn't have
caused this". If excerpts from the damaged image are any help in
finding the actual issue, I can keep it around for a while.

Disaster recovery. What do people use to quickly get back up and
running from bare metal that integrates well with btrfs (and is
suitable just for a handful of machines)?

Cheers,
C.

P.S.: MemTest86 hasn't found anything in (as yet) 6 passes, nothing
glaringly wrong with the RAM.

  reply	other threads:[~2019-10-24 10:42 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAKbQEqE7xN1q3byFL7-_pD=_pGJ0Vm9pj7d-g+rRgtONeH-GrA@mail.gmail.com>
2019-10-19 22:34 ` first it froze, now the (btrfs) root fs won't mount Christian Pernegger
2019-10-20  0:38   ` Qu Wenruo
2019-10-20 10:11     ` Christian Pernegger
2019-10-20 10:22       ` Christian Pernegger
2019-10-20 10:28         ` Qu Wenruo
2019-10-21 10:47           ` Christian Pernegger
2019-10-21 10:55             ` Qu Wenruo
2019-10-21 11:47             ` Austin S. Hemmelgarn
2019-10-21 13:02               ` Christian Pernegger
2019-10-21 13:34                 ` Qu Wenruo
2019-10-22 22:56                   ` Christian Pernegger
2019-10-23  0:25                     ` Qu Wenruo
2019-10-23 11:31                     ` Austin S. Hemmelgarn
2019-10-24 10:41                       ` Christian Pernegger [this message]
2019-10-24 11:26                         ` Qu Wenruo
2019-10-24 11:40                         ` Austin S. Hemmelgarn
2019-10-25 16:43                           ` Christian Pernegger
2019-10-25 17:05                             ` Christian Pernegger
2019-10-25 17:16                               ` Austin S. Hemmelgarn
2019-10-25 17:12                             ` Austin S. Hemmelgarn
2019-10-26  0:01                             ` Qu Wenruo
2019-10-26  9:23                               ` Christian Pernegger
2019-10-26  9:41                                 ` Qu Wenruo
2019-10-26 13:52                                   ` Christian Pernegger
2019-10-26 14:06                                     ` Qu Wenruo
2019-10-26 16:30                                       ` Christian Pernegger
2019-10-27  0:46                                         ` Qu Wenruo
     [not found]                                           ` <CAKbQEqFne8eohE3gvCMm8LqA-KimFrwwvE5pUBTn-h-VBhJq1A@mail.gmail.com>
2019-10-27 13:38                                             ` Qu Wenruo
2019-10-21 14:02                 ` Austin S. Hemmelgarn

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='CAKbQEqGoiGbV+Q=LVfSbKLxYeQ5XmLFMMBdq_yxSR7XE3SwsmA@mail.gmail.com' \
    --to=pernegger@gmail.com \
    --cc=ahferroin7@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=quwenruo.btrfs@gmx.com \
    /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.