From: "J. Ellis" <jellis@dhnet.us>
To: stan@hardwarefreak.com, xfs@oss.sgi.com
Subject: Re: xfsdump INTERRUPT issue
Date: Tue, 04 Dec 2012 20:18:31 -0500 [thread overview]
Message-ID: <CCE40B17.B056E%jellis@dhnet.us> (raw)
In-Reply-To: <50BE961B.8030705@hardwarefreak.com>
Hi, Stan--
Ok, I truly apologize for my ignorance, but I don't know how to dump the
contents to a file. Is it something like:
xfsdump -J - somefile_xfsdump.txt
xfsrestore -J - somefile_xfsrestore.txt
?
Best,
J.
on 12/4/12 7:32 PM, Stan Hoeppner at stan@hardwarefreak.com wrote:
> On 12/3/2012 4:27 PM, Jeffrey Ellis wrote:
>
> xfs_info output and this below is all that is needed at this point.
>
>>> FWIW, this implies that xfsrestore failed. What is the output from
>>> xfsrestore? Can you just run xfsdump to a file?
>
>> Can you tell me how to do that and dmesg?
>
> The command you posted
>
> xfsdump -J - /mnt/hr20 | xfsrestore -J - /mnt/fp
>
> pipes the output from xfsdump into xfsrestore. This error
>
> xfsdump: WARNING: write to stdio failed: 32 (Broken pipe)
>
> tells us something broke while piping into xfsrestore, possibly
> xfsrestore itself. I believe what Dave is asking you is to xfsdump to a
> file, then xfsrestore that file. In two separate operations. This
> should tell us more about where the problem is.
>
> Regarding dmesg information, simply do
>
> ~$ dmesg
>
> and copy the output into your email. It should be a few screen fulls
> starting with something like:
>
> Linux version 3.2.6 (root@greer) (gcc version 4.4.5 (Debian 4.4.5-8) )
> #1 SMP Mon Feb 20 17:05:10 CST 2012
>
> WRT xfs_info:
>
> ~$ cat /etc/mtab
> ...
> /dev/sda6 /home xfs rw 0 0
> ...
>
> ~$ xfs_info /dev/sda6
> meta-data=/dev/sda6 isize=256 agcount=4, agsize=6103694 blks
> = sectsz=512 attr=2
> data = bsize=4096 blocks=24414775, imaxpct=25
> = sunit=0 swidth=0 blks
> naming =version 2 bsize=4096 ascii-ci=0
> log =internal bsize=4096 blocks=11921, version=2
> = sectsz=512 sunit=0 blks, lazy-count=0
> realtime =none extsz=4096 blocks=0, rtextents=0
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-12-05 1:16 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 [this message]
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
[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=CCE40B17.B056E%jellis@dhnet.us \
--to=jellis@dhnet.us \
--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