From: Dave Chinner <david@fromorbit.com>
To: Stan Hoeppner <stan@hardwarefreak.com>
Cc: Jeffrey Ellis <grndlvl@gmail.com>, "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: xfsdump INTERRUPT issue
Date: Fri, 7 Dec 2012 21:16:21 +1100 [thread overview]
Message-ID: <20121207101620.GK27172@dastard> (raw)
In-Reply-To: <50C0657D.5050903@hardwarefreak.com>
On Thu, Dec 06, 2012 at 03:29:33AM -0600, Stan Hoeppner wrote:
> On 12/5/2012 9:01 PM, Jeffrey Ellis wrote:
> BTW, if your goal in all of this is simply copying all the directories
> and files from one disk to another disk, you could have used "cp -a" and
> been done already. It takes longer to execute than xfsdump/xfsrestore,
> but given you've been at this for many days now, "cp -a" would have
> already completed--long ago.
Unfortunately, using cp or rsync is not possible because the
filesystem has a real-time device attached to it. It's basically a
~10GB data device and a ~500GB real-time device. I'd say it's from a
DVR or something like that, and that Jeffrey is trying to put
a bigger disk in the DVR....
Hence there are various DVR forums that suggest xfsdump/xfsrestore
is the best method for copying such filesystems to a larger disk.
I'd guess that people haven't found xfs_rtcp, or maybe they saw the
caveat in the man page(*) and didn't use it....
Cheers,
Dave.
(*) CAVEATS
Currently, realtime partitions are not supported under the
Linux version of XFS, and use of a realtime partition WILL
CAUSE CORRUPTION on the data partition. As such, this command
is made available for curious DEVELOPERS ONLY at this
point in time.
--
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:[~2012-12-07 10:14 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CCE505AA.B05B7%jellis@dhnet.us>
2012-12-06 1:38 ` xfsdump INTERRUPT issue Stan Hoeppner
2012-12-06 2:08 ` Jeffrey Ellis
2012-12-06 2:40 ` Stan Hoeppner
[not found] ` <6F909666-9DFE-43F1-973D-170B892F9C5B@gmail.com>
2012-12-06 9:29 ` Stan Hoeppner
2012-12-06 10:35 ` Jeffrey Ellis
2012-12-07 10:16 ` Dave Chinner [this message]
2012-12-07 16:15 ` Jeffrey Ellis
2012-12-07 22:59 ` Dave Chinner
2012-12-07 23:16 ` Jeffrey Ellis
2012-12-07 21:04 ` Stan Hoeppner
2012-12-07 22:58 ` Dave Chinner
2012-12-07 23:26 ` Stan Hoeppner
2012-12-08 1:31 ` Dave Chinner
2012-12-01 16:03 J. Ellis
2012-12-01 17:39 ` Jeffrey Ellis
2012-12-02 1:40 ` Stan Hoeppner
2012-12-03 16:49 ` J. Ellis
2012-12-03 21:34 ` Dave Chinner
2012-12-03 22:27 ` Jeffrey Ellis
2012-12-05 0:32 ` Stan Hoeppner
2012-12-05 1:18 ` J. Ellis
2012-12-05 3:32 ` Stan Hoeppner
2012-12-04 19:46 ` J. Ellis
2012-12-04 22:56 ` Stan Hoeppner
2012-12-04 23:07 ` Jeffrey Ellis
2012-12-05 22:19 ` Dave Chinner
2012-12-02 21:10 ` Dave Chinner
2012-12-02 21:16 ` Jeffrey Ellis
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=20121207101620.GK27172@dastard \
--to=david@fromorbit.com \
--cc=grndlvl@gmail.com \
--cc=stan@hardwarefreak.com \
--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