unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Raghav Gururajan <raghavgururajan@disroot.org>
To: Mark H Weaver <mhw@netris.org>,
	Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 43132-done@debbugs.gnu.org
Subject: bug#43132: [GUIX SYSTEM]: Malfunction
Date: Tue, 15 Sep 2020 18:38:46 -0400	[thread overview]
Message-ID: <dd7e1230-04a4-de06-fdb9-2bbdd4c684c0@disroot.org> (raw)
In-Reply-To: <871rj2bsdt.fsf@netris.org>


[-- Attachment #1.1: Type: text/plain, Size: 918 bytes --]

Hi Mark and Maxim!

>> Ext4 won't detect bitrot (silent corruption of your drive's data).
>> You'll probably wake one day with a fsck that won't be able to recover
>> some files, or worst, a completely dead drive.
>>
>> Your backups would also contain corrupted data (garbage in, garbage
>> out!).
> 
> For what it's worth, I wholeheartedly agree with Maxim.  Btrfs did you a
> great service by calling attention to this problem with your drive, and
> it would be a shame to ignore it and switch back to ext4 where your data
> may instead be silently corrupted.
> 
> I've been using btrfs for several years now on my x86_64 Guix system,
> and it has served me well.  Previously, I used ext4, which would
> silently leave some of my files empty after crashes.  I've never seen
> that happen with btrfs.

Yeah, makes sense. I have placed an order for WDS100T2B0A.

Thanks folks!

Regards,
RG.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2020-09-15 23:00 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
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 [this message]

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=dd7e1230-04a4-de06-fdb9-2bbdd4c684c0@disroot.org \
    --to=raghavgururajan@disroot.org \
    --cc=43132-done@debbugs.gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    --cc=mhw@netris.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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).