[Top] [All Lists]

Re: xfsdump INTERRUPT issue

To: xfs@xxxxxxxxxxx
Subject: Re: xfsdump INTERRUPT issue
From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Date: Tue, 04 Dec 2012 21:32:43 -0600
In-reply-to: <CCE40B17.B056E%jellis@xxxxxxxx>
References: <CCE40B17.B056E%jellis@xxxxxxxx>
Reply-to: stan@xxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/17.0 Thunderbird/17.0
On 12/4/2012 7:18 PM, J. Ellis wrote:
> 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

~$ man xfsdump

Look at option "-f".

> xfsrestore -J - somefile_xfsrestore.txt

~$ man xfsrestore

See options "-f" "-t" and "-v".

The point of this exercise I believe is to see what errors are thrown by
xfsdump or xfsrestore when they are executed independently, vs through a
pipe.  Do note that this may not be the final step in testing before you
have an answer.  Post any errors or informational output that results
from these commands.

Note that the file written by xfsdump is going to be about the same size
as the filesystem being dumped.  I.e. if the filesystem being dumped is
1TB then you need 1TB of free space on the device where the target
directory resides--you're dumping an entire XFS filesystem into a single
file.  Also, be sure to use "-t" so xfsrestore doesn't actually write
anything.  Did you read "-v"?


<Prev in Thread] Current Thread [Next in Thread>