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
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
~$ 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