linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Forrest Aldrich <forrie@gmail.com>
To: Forza <forza@tnonline.net>, "Eu, acc" <accensi@gmail.com>,
	dsterba@suse.cz, linux-btrfs@vger.kernel.org
Subject: Re: APFS and BTRFS
Date: Sat, 27 Mar 2021 14:16:26 -0400	[thread overview]
Message-ID: <085b131d-58ce-bfe3-16d9-e02bc3d01ba4@gmail.com> (raw)
In-Reply-To: <43aa98ff-edfb-fba8-1bbb-2c497fbbe89e@tnonline.net>

I'm taking data from the 18TB drive and placing it onto the USB-drive 
array I built (slower) -- it's on a USB 3.0 bus, off a raspberry pi, so 
very limited in terms of what I can do for that. It's a hackup job I'm 
building for longer term storage.  The real bottleneck is the USB3.x bus 
and the USB-based disks I have striped together -- yes, i know it's a 
hack :)



On 3/27/21 2:13 PM, Forza wrote:
>
> On 2021-03-23 00:19, Forrest Aldrich wrote:
>> I have apfs-fuse running, but it is read-only.
>>
>> I wanted to avoid the pain of replicating a large disk from USB3 to 
>> USB3 by converting the filesystem, which I expected wouldn't be 
>> possible.  So now I am just replicating it, which will take days to 
>> accomplish.
>>
> Have you considered taking the disks out of the USB enclosure and 
> putting them directly on the SATA controller? It could be faster.
>
>
> ~Forza


  reply	other threads:[~2021-03-27 18:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-20 15:22 APFS and BTRFS Forrest Aldrich
2021-03-22 22:22 ` David Sterba
     [not found]   ` <CAA+gEba91br_M6qERcwL5no=DdMSw3QA7iNwf8OGwskX=9Z6_g@mail.gmail.com>
2021-03-22 23:19     ` Forrest Aldrich
2021-03-27 18:13       ` Forza
2021-03-27 18:16         ` Forrest Aldrich [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-03-20 16:09 Forrest Aldrich
2021-04-04 13:45 ` Michal Rostecki

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=085b131d-58ce-bfe3-16d9-e02bc3d01ba4@gmail.com \
    --to=forrie@gmail.com \
    --cc=accensi@gmail.com \
    --cc=dsterba@suse.cz \
    --cc=forza@tnonline.net \
    --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;
as well as URLs for NNTP newsgroup(s).