all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 43132-done@debbugs.gnu.org,
	Raghav Gururajan <raghavgururajan@disroot.org>
Subject: bug#43132: [GUIX SYSTEM]: Malfunction
Date: Mon, 14 Sep 2020 11:14:28 -0400	[thread overview]
Message-ID: <87363k5r1n.fsf@gmail.com> (raw)
In-Reply-To: <87h7s6jc98.fsf@gnu.org> ("Ludovic Courtès"'s message of "Thu, 10 Sep 2020 09:56:35 +0200")

Hello,

Ludovic Courtès <ludo@gnu.org> writes:

> Hey Raghav,
>
> Did you eventually find what went wrong?  Should we close this bug or at
> least retitle it?
>
> Thanks,
> Ludo’.

I took Raghav to #btrfs last week, where with the help of gentle folks a
failing drive was established as the most likely culprit.

In other words, Btrfs checksuming capabilities helped quickly
discovering a hardware problem which might otherwise have silently
caused non-recoverable damage to Raghav's data.

I'm closing this bug now.

Thanks!

Maxim




  reply	other threads:[~2020-09-14 15:56 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-31  9:48 bug#43132: [GUIX SYSTEM]: Malfunction Raghav Gururajan
2020-08-31  9:53 ` Efraim Flashner
2020-08-31 10:01   ` Raghav Gururajan
2020-08-31 10:39 ` Giovanni Biscuolo
2020-08-31 10:48   ` Raghav Gururajan
2020-08-31 11:11     ` Giovanni Biscuolo
2020-08-31 12:07       ` Julien Lepiller
2020-08-31 12:40         ` Giovanni Biscuolo
2020-08-31 21:17 ` Danny Milosavljevic
2020-09-01  3:04   ` Raghav Gururajan
2020-09-01  7:58     ` Danny Milosavljevic
2020-09-10  7:56     ` Ludovic Courtès
2020-09-14 15:14       ` Maxim Cournoyer [this message]
2020-09-14 19:34         ` Ludovic Courtès
2020-09-15 11:51           ` Raghav Gururajan
2020-09-15 13:31             ` Maxim Cournoyer
2020-09-15 22:13               ` Mark H Weaver
2020-09-15 22:38                 ` Raghav Gururajan

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=87363k5r1n.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=43132-done@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    --cc=raghavgururajan@disroot.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. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

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.