public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Torsten Bronger <bronger@physik.rwth-aachen.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: Why is converting from RAID1 to single in Btrfs an I/O-intensive operation?
Date: Sun, 19 Feb 2023 20:04:28 +0100	[thread overview]
Message-ID: <87k00dmq83.fsf@physik.rwth-aachen.de> (raw)
In-Reply-To: 8531c30e-885b-1d8d-314b-5167ed0874ac@libero.it

Hallöchen!

Goffredo Baroncelli writes:

> [...] 
>
> Just for curiosity, I know that the BTRFS RAID1 is not the fastest
> implementation, but how slower is in your "I/O-intensive
> operation".

What exactly do you want to compare?  Be that as it may, I have no
benchmarks.  Originally, I was just wondering why RAID1 --> single
may take hours, given that all data is on both disks anyway.

Regards,
Torsten.

-- 
Torsten Bronger


  reply	other threads:[~2023-02-19 19:11 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-18  8:10 Why is converting from RAID1 to single in Btrfs an I/O-intensive operation? Torsten Bronger
2023-02-18  8:54 ` Andrei Borzenkov
2023-02-18 11:32   ` Torsten Bronger
2023-02-18 10:46 ` Goffredo Baroncelli
2023-02-18 11:38   ` Torsten Bronger
2023-02-18 17:47     ` me
2023-02-18 20:05       ` Torsten Bronger
2023-02-18 21:46         ` me
2023-02-19 10:09     ` Goffredo Baroncelli
2023-02-19 19:04       ` Torsten Bronger [this message]
2023-02-19 23:39         ` waxhead
2023-02-20  6:31           ` Torsten Bronger
2023-02-20  9:38             ` Patrik Lundquist
2023-02-20 15:48           ` Forza
2023-02-21  7:18             ` Torsten Bronger
2023-02-21 11:35               ` me
2023-02-22  8:30                 ` Torsten Bronger
2023-02-26 18:52     ` Ferry Toth

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=87k00dmq83.fsf@physik.rwth-aachen.de \
    --to=bronger@physik.rwth-aachen.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox