linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hubert Kario <hka@qbs.com.pl>
To: Lubos Kolouch <lubos.kolouch@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Copy/move btrfs volume
Date: Wed, 21 Jul 2010 17:00:12 +0200	[thread overview]
Message-ID: <201007211700.38453.hka@qbs.com.pl> (raw)
In-Reply-To: <i0mp3v$q93$1@dough.gmane.org>

On Saturday 03 July 2010 09:33:19 Lubos Kolouch wrote:
> Oystein Viggen, Fri, 02 Jul 2010 08:15:03 +0200:
> > For btrfs with lots of snapshots, I believe "btrfs device add" of t=
he
> > new device followed by "btrfs device remove" of the old one would b=
e the
> > most convenient.
> >=20
> > =C3=98ystein
>=20
> This solution if very elegant and cool - if you can put the discs int=
o one
> computer.
>=20
> It does not help too much to copy the files over network and preserve=
 the
> snapshots... or can you add like this a network-attached device (sshf=
s) ?

You could also go the totally cool option (albeit a bit creazy) and use=
=20
network block devices and have no downtime...

The overall process will take more time though.

--=20
Hubert Kario
QBS - Quality Business Software
ul. Ksawer=C3=B3w 30/85
02-656 Warszawa
POLAND
tel. +48 (22) 646-61-51, 646-74-24
fax +48 (22) 646-61-50
--
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

  reply	other threads:[~2010-07-21 15:00 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
2010-07-03  7:33         ` Lubos Kolouch
2010-07-21 15:00           ` Hubert Kario [this message]
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=201007211700.38453.hka@qbs.com.pl \
    --to=hka@qbs.com.pl \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lubos.kolouch@gmail.com \
    /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).