From: Dave Chinner <david@fromorbit.com>
To: "Meij, Henk" <hmeij@wesleyan.edu>
Cc: Eric Sandeen <sandeen@sandeen.net>, "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: clone of filesystem across network preserving ionodes
Date: Tue, 4 Nov 2014 08:56:04 +1100 [thread overview]
Message-ID: <20141103215604.GA23575@dastard> (raw)
In-Reply-To: <8688BD11DAC0574AA90295127E9E9F4AC047F22D@exchangewes8.wesad.wesleyan.edu>
On Mon, Nov 03, 2014 at 09:10:10PM +0000, Meij, Henk wrote:
> inodes, yes, yes. I tried xfs_copy but ran into a problem.
> server1 and server2 each have 4x28T partitions and on server1
> writing the file to one empty partition mounted never finishes,
> hangs at 90%...presumably because it runs out of space (file size
> == sdbx).
Sure, but it's a sparse copy. It only copies the allocated blocks in
the filesystem, so the actual space required is the used space int
eh filesystem (i.e. what df reports as used).
> there is no "skip empty inodes" option and perhaps there
> can't be...
Of course not - you're wanting identical inode numbers on
either end, so your only option is and identical copy. Otherwise
you'd use xfsdump/xfsrestore to skip empty inodes...
> and I have nothing larger. I guess I could attempt
> making sdb4 slightly larger by reducing sdb1-3.
Exactly why do you need an *identical* copy of 28TB filesystems?
What is the problem with inode numbers being different? And that
begs the question: if you need the filesystems to be completely
identical yet exist on separate systems, then why aren't you using a
block layer construct designed for such operation (e.g. drdb)?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-11-03 21:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-03 20:35 clone of filesystem across network preserving ionodes Meij, Henk
2014-11-03 20:39 ` Eric Sandeen
2014-11-03 21:10 ` Meij, Henk
2014-11-03 21:56 ` Dave Chinner [this message]
2014-11-04 0:05 ` Peter Grandi
2014-11-04 14:16 ` Meij, Henk
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=20141103215604.GA23575@dastard \
--to=david@fromorbit.com \
--cc=hmeij@wesleyan.edu \
--cc=sandeen@sandeen.net \
--cc=xfs@oss.sgi.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