From: Oystein Viggen <oysteivi@tihlde.org>
To: linux-btrfs@vger.kernel.org
Subject: Re: Copy/move btrfs volume
Date: Fri, 02 Jul 2010 08:15:03 +0200 [thread overview]
Message-ID: <03lj9ujtp4.fsf@msgid.viggen.net> (raw)
In-Reply-To: 4C2D14DA.3040301@gmx.com
* [Matt Brown]=20
> With backed up files consisting of hard links, I usually use dd to co=
py
> the file systems at the block level
>
> # dd if=3D/dev/sda of=3D/dev/sdb bs=3D20M
>
> and then expand the file system. This is because I found that tools l=
ike
> rsync, while usually fast, are extremely slow when dealing with milli=
ons
> of hard linked files.
>
> This could also be used for btrfs to keep its snapshots.
If you can (temporarily) attach the old and new drives to the same
computer, putting the ext4 BackupPC store on LVM and moving the LV
around might be more convenient, or at least feel more "high level".
=46or btrfs with lots of snapshots, I believe "btrfs device add" of the
new device followed by "btrfs device remove" of the old one would be th=
e
most convenient.
One advantage of using LVM and btrfs multi device support in this way i=
s
that the actual downtime is minimal -- you can keep the filesystems
online. Even on cheap hardware, the only downtime should be to
attach/remove disks.
=D8ystein
--=20
If it ain't broke, don't break it.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-07-02 6:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-01 10:28 Copy/move btrfs volume Lubos Kolouch
2010-07-01 11:26 ` Daniel J Blueman
2010-07-01 11:33 ` Lubos Kolouch
2010-07-01 22:21 ` Matt Brown
2010-07-02 6:15 ` Oystein Viggen [this message]
2010-07-03 7:33 ` Lubos Kolouch
2010-07-21 15:00 ` Hubert Kario
2010-07-02 1:29 ` Chris Mason
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=03lj9ujtp4.fsf@msgid.viggen.net \
--to=oysteivi@tihlde.org \
--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).