From: Roman Mamedov <rm@romanrm.net>
To: David Schiller <david.schiller@jku.at>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Question about 32 bit limitations
Date: Thu, 18 Jul 2024 18:50:19 +0500 [thread overview]
Message-ID: <20240718185019.74f76e5e@nvm> (raw)
In-Reply-To: <4426d5d3202c37b9bc7cea5281c017f77521074b.camel@jku.at>
On Thu, 18 Jul 2024 13:02:25 +0200
David Schiller <david.schiller@jku.at> wrote:
> I don't want to decommission this box, so the alternative would be to
> recreate the file system from scratch and restore from backup. This is a
> very low priority system, that's why I ignored the warning initially.
> This is by no means the fault of BTRFS.
As an option, you can avoid mounting the disks on the box itself, and instead
export them via NBD, AoE or iSCSI to be mounted on another box.
I run a very old DNS-323 armv5 NAS with just 64 MB of RAM, exporting a 6 TB
disk over NBD. (qemu-nbd was the only NBD server that works well given the
limitations). Every day my amd64 server temporarily mounts the NBD device,
runs rsync to it, then unmounts and disconnects until the next backup.
In your case it would be a bit more involved to export 4 devices and then
ensure all are connected remotely on the other machine before mounting. But
not impossible with a bit of scripting.
--
With respect,
Roman
next prev parent reply other threads:[~2024-07-18 13:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-18 11:02 Question about 32 bit limitations David Schiller
2024-07-18 13:50 ` Roman Mamedov [this message]
2024-07-18 14:08 ` David Schiller
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=20240718185019.74f76e5e@nvm \
--to=rm@romanrm.net \
--cc=david.schiller@jku.at \
--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