public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Anthony l <Martinezant2141@live.com>
Cc: Andrew Ho <andrewho@animezone.org>,
	Eric Sandeen <sandeen@sandeen.net>,
	"xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: Question: Old Irix tape backup. Recovery on Linux (xfsdump/xfsrestore)
Date: Mon, 4 Jul 2016 10:15:40 +1000	[thread overview]
Message-ID: <20160704001540.GX12670@dastard> (raw)
In-Reply-To: <SN1PR05MB23179FAACBDA0B885FE11D06CC250@SN1PR05MB2317.namprd05.prod.outlook.com>

On Fri, Jul 01, 2016 at 06:23:21PM +0000, Anthony l wrote:
> But I do have an observation. I had a tape (not made on the irix
> system) and I was able to pull a direct transfer of files with the
> dd command. i.e dd if=/dev/nst0 of=./somefile1 ibs =64k
> 
> And I would only have to do this 3 -4 times to get like 30+ GBs of
> data off the tapes and a simple tar xvf command extracted these
> files just fine. But my question is how come when I try to do
> these with the tapes made on the Irix machine I only get about 200
> mb at a time and there are like 190+ files on each tape. Is this
> normal for an xfs file system on a tape drive?

>From the xfsrestore man page:

Media Errors

       xfsdump  is  tolerant of media errors, but cannot do error
       correction.  If a media error occurs in the body of a media
       file, the filesystem file represented at that point is lost.
       The bad portion of the media is skipped, and the restoration
       resumes at the next filesystem file after the bad portion of
       the media.

       If a media error occurs in the beginning of the media file,
       the entire media file is lost.  For this reason, large dumps
       are broken into a number of reasonably sized media files.
       The restore resumes with the next media file.


The error you are seeing is with the last media file in the dump
which, IIRC, contains critical inventory information and so restore
cannot continue without that media file. You need to work out why
that last media file is returning a short read, once once you solve
that problem xfsrestore should work correctly.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  parent reply	other threads:[~2016-07-04  0:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-29 18:48 Question: Old Irix tape backup. Recovery on Linux (xfsdump/xfsrestore) Anthony l
2016-06-29 19:29 ` Eric Sandeen
2016-06-29 22:17 ` Dave Chinner
2016-06-30 15:35 ` Anthony l
2016-06-30 16:11   ` Eric Sandeen
2016-06-30 16:59     ` Anthony l
2016-06-30 17:04       ` Eric Sandeen
2016-06-30 17:39         ` Anthony l
2016-06-30 22:07         ` Dave Chinner
2016-07-01  4:44           ` Andrew Ho
2016-07-01 18:23             ` Anthony l
2016-07-01 19:28               ` Roger Willcocks
2016-07-05 17:01                 ` Anthony l
2016-07-04  0:15               ` Dave Chinner [this message]
2016-07-05 18:21                 ` Roger Willcocks

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=20160704001540.GX12670@dastard \
    --to=david@fromorbit.com \
    --cc=Martinezant2141@live.com \
    --cc=andrewho@animezone.org \
    --cc=sandeen@sandeen.net \
    --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