unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Fredrik Salomonsson <plattfot@gmail.com>
To: Giovanni Biscuolo <g@xelera.eu>, help-guix@gnu.org
Subject: Re: btrfs raid configuration vs mdraid
Date: Tue, 21 May 2019 09:35:36 -0700	[thread overview]
Message-ID: <87o93vlq93.fsf@gmail.com> (raw)
In-Reply-To: <871s0s9ptj.fsf@roquette.mug.biscuolo.net>


Hi Giovanni,

Giovanni Biscuolo <g@xelera.eu> writes:

[...]

>>> Assuming I'm going to format the root filesystem as:
>>>
>>>   mkfs.btrfs -m raid1 -d raid1 /dev/sda3 /dev/sdb3
>>>
>>> how should I configure (file-system...)? this way:
>>>
>>> (file-system
>>>   (mount-point "/")
>>>   (type "btrfs")
>>>   (device (uuid "4dab5feb-d176-45de-b287-9b0a6e4c01cb")))
>>>
>>> with UUID taken from "lsblk -f"?
>>
>> That should work.
>
> I confirm it worked, easily! :-)

Good to know :).

[...]

>> One thing you should note is that guix might generate incorrect
>> paths for grub if you are using subvolumes. At least guix < 1.0 does
>> that for me, haven't tested 1.0+ yet. But I have been using a shell
>> script that works around that issue.
>
> I did not use root on a subvolume for my installation, but I'll try to
> reproduce it in a test install: can you please file a bug report for
> this, IMHO this should be fixed

Looks like there is already a bug report on this:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=33517

And I just tested to reconfigure my system with guix v1.0.1 and the
issue is still there.

>>> From you experience is RAID on brtfs as solid as the one on mdadm?
>>
>> I have very little experience with mdadm, so can only speak of my
>> experience with btrfs and RAID-1. Which I have been using for 3+ years.
>> For me it has been solid. Only issue I have encountered was when my
>> fileserver lost power a few times leaving the filesystem corrupt. A
>> "btrfs check --repair" fixed that issue.
>
> Thanks for sharing! You give me courage to adopt btrfs more extensively
> :-)

Glad I could help out.

--
s/Fred[re]+i[ck]+/Fredrik/g

      reply	other threads:[~2019-05-21 16:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-16  6:00 btrfs raid configuration vs mdraid Giovanni Biscuolo
2019-05-20 19:59 ` Fredrik Salomonsson
2019-05-21  8:25   ` Giovanni Biscuolo
2019-05-21 16:35     ` Fredrik Salomonsson [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=87o93vlq93.fsf@gmail.com \
    --to=plattfot@gmail.com \
    --cc=g@xelera.eu \
    --cc=help-guix@gnu.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 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).