From: "J. Ellis" <jellis@dhnet.us>
To: Jeffrey Ellis <jellis@dhnet.us>,
stan@hardwarefreak.com, Dave Chinner <david@fromorbit.com>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: xfsdump INTERRUPT issue
Date: Tue, 04 Dec 2012 14:46:53 -0500 [thread overview]
Message-ID: <CCE3BD5D.B0540%jellis@dhnet.us> (raw)
In-Reply-To: <CCE2425A.B0475%jellis@dhnet.us>
Hi, Dave & Stan, et al--
Are you guys getting this post? I don't see it showing up on the list and
have had no responses. I'm wondering if the size of the text of the
requested xfs info I had added is causing an issue getting it posted.
If not, here's a repost, using a link to the file instead.
http://dhnet.us/xfs/xfs_data_file.odt
Best,
Jeffrey
on 12/3/12 11:49 AM, Jeffrey Ellis at jellis@dhnet.us wrote:
> Thank you to Stan and Dave for helping me through this.
>
> Ok, here's the file, printed below.
>
> Basically, I'm running the following commands under Ubuntu 12.10:
>
> Type mkdir /mnt/fp
> Type mkdir /mnt/hr20
> Type mount -t xfs -o rtdev=/dev/sda3 /dev/sda2 /mnt/fp
> Type mount -t xfs -o rtdev=/dev/sdb3 /dev/sdb2 /mnt/hr20
> Type xfsdump -J - /mnt/hr20 | xfsrestore -J - /mnt/fp
>
> When run, I get this as my output:
>
> xfsdump: WARNING: write to stdio failed: 32 (Broken pipe)
> xfsdump: ending media file
> xfsdump: media file size 18874368 bytes
> xfsdump: dump size (non-dir files) : 13698056 bytes
> xfsdump: NOTE: dump interrupted: 16 seconds elapsed
> xfsdump: Dump Status: INTERRUPT
>
> This happens each time. In the forum where this copy procedure was
> suggested, they've been reporting that the latest xfsprogs is creating these
> errors, which didn't happen under at least somewhat earlier versions.
>
> The version of xfsprogs should be in the file, but it was just downloaded a
> few days ago using git.
>
> Best,
> Jeffrey
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-12-04 19:44 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-01 16:03 xfsdump INTERRUPT issue 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 [this message]
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
[not found] <CCE505AA.B05B7%jellis@dhnet.us>
2012-12-06 1:38 ` 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
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
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=CCE3BD5D.B0540%jellis@dhnet.us \
--to=jellis@dhnet.us \
--cc=david@fromorbit.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