From: Frank Steinmetzger <Warp_7@gmx.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: How to move ext4 partition
Date: Thu, 21 Sep 2023 00:12:16 +0200 [thread overview]
Message-ID: <ZQtuQDyotLN8r2ss@kern> (raw)
In-Reply-To: <CAB=_hA6GRyGOjuESZynkJjXE=uRpr-n-mioC4dGuyTav9sWikA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1579 bytes --]
Am Wed, Sep 20, 2023 at 10:57:00PM +0100 schrieb Victor Ivanov:
> On Wed, 20 Sept 2023 at 22:29, Grant Edwards <grant.b.edwards@gmail.com> wrote:
> >
> > That depends on how long it takes me to decide on tar vs. rsync and
> > what the appropriate options are.
>
> I've done this a number of times for various reasons over the last 1-2
> years, most recently a few months ago due to hard drive swap, and I
> find tar works just fine:
>
> $ tar -cpf /path/to/backup.tar --xattrs --xattrs-include='*.*' -C / .
Does that stop at file system boundaries (because you tar up '/')? I think
it must be, otherwise you wouldn’t use it that way.
But when copying a root file system, out of habit I first bind-mount it in a
subdirectory and tar/rsync from there instead. This will also make files
visible which might be hidden under an active mount.
This is not necessary if you do it from a live system, but then you wouldn’t
tar up / in the first place.
> Likewise to extract, but make sure "--xattrs" is present
>
> Provided backup space isn't an issue, I wouldn't bother with
> compression. It could be a lot quicker too depending on the size of
> your root partition.
Or not, depending on the speed of the backup device. ;-)
LZO compression (or zstd with a low setting) has negligible CPU cost, but
can lower the file size quite nicely, specially with large binaries or debug
files.
--
Grüße | Greetings | Salut | Qapla’
Please do not share anything from, with or about me on any social network.
Do you steel taglines, too?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-09-20 22:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 20:24 [gentoo-user] How to move ext4 partition Grant Edwards
2023-09-20 21:16 ` Neil Bothwick
2023-09-20 21:28 ` [gentoo-user] " Grant Edwards
2023-09-20 21:57 ` Victor Ivanov
2023-09-20 22:12 ` Frank Steinmetzger [this message]
2023-09-20 23:03 ` Grant Edwards
2023-09-21 9:20 ` Victor Ivanov
2023-09-20 22:58 ` Grant Edwards
2023-09-21 9:32 ` Victor Ivanov
2023-09-21 20:23 ` Grant Edwards
2023-09-21 21:39 ` Jack
2023-09-21 22:17 ` Grant Edwards
2023-09-20 23:03 ` Neil Bothwick
2023-09-20 21:37 ` [gentoo-user] " Wol
2023-09-20 22:39 ` [gentoo-user] " Grant Edwards
2023-09-22 6:48 ` Wols Lists
2023-09-23 12:16 ` Håkon Alstadheim
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=ZQtuQDyotLN8r2ss@kern \
--to=warp_7@gmx.de \
--cc=gentoo-user@lists.gentoo.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