Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 2 Oct 1998 13:28:02 -0700 (PDT)
From:      Jacob Ritorto <jritorto@tsoft.net>
To:        Thomas David Rivers <rivers@dignus.com>
Cc:        freebsd-questions@FreeBSD.ORG
Subject:   Re: migrating to FreeBSD
Message-ID:  <Pine.BSF.4.01.9810021327090.2724-100000@juniper.tsoft.net>
In-Reply-To: <199810022000.QAA01121@lakes.dignus.com>

next in thread | previous in thread | raw e-mail | index | archive | help


On Fri, 2 Oct 1998, Thomas David Rivers wrote:

>  I don't know much about the floppy tape's though; or the suspicious
> "Linux raw format v2" - (is that the label you put on the tapes?)

No, linux did that itself.

> 
>  But - you should be able to access the raw device... are you root?
> 

Ain't happenin'.  That's why I sent the typescript (see near end of it).


> > 
> > >From root@.MISSING-HOST-NAME. Fri Oct  2 12:44:36 1998
> > Date: Fri, 2 Oct 1998 12:43:25 -0700 (PDT)
> > From: Charlie Root <root>
> > To: jritorto
> > 
> > Script started on Fri Oct  2 12:39:24 1998
> > sh-2.02# tar -xvFM^H ^H^H ^H^H ^HvMf -^H^H^H^H^H^H^H^H^H^H^H^G^[[1@ft^[[1@t^H^[[1@ ^[[1@|^[[1@ 
> > Incorrect volume inserted.  This tape is:
> > "Linux raw format V2" - Mon Apr 27 00:17:50 1998
> > 
> > Insert ftfilt volume 01 and press enter:Linux raw format v2^H ^H^H ^HV2"^H ^H
> > ft: using secondary header
> > Incorrect volume inserted.  This tape is:
> > "Linux raw format V2" - Mon Apr 27 00:17:50 1998
> > 
> > Insert ftfilt volume 01 and press enter:ft: waiting for drive to become ready
> > ft: using secondary header
> > Incorrect volume inserted.  This tape is:
> > "Linux raw format V2" - Mon Apr 27 00:17:50 1998
> > 
> > Insert ftfilt volume 01 and press enter:ft: waiting for drive to become ready
> > ft: using secondary header
> > Incorrect volume inserted.  This tape is:
> > "Linux raw format V2" - Mon Apr 27 00:17:50 1998
> > 
> > Insert ftfilt volume 01 and press enter:ft: waiting for drive to become ready
> > ft: using secondary header
> > Incorrect volume inserted.  This tape is:
> > "Linux raw format V2" - Mon Apr 27 00:17:50 1998
> > 
> > Insert ftfilt volume 01 and press enter:ft: waiting for drive to become ready
> > ^C^C^C^C^C^C^C^C^C^C^C^C
> > sh-2.02# 
> > sh-2.02# ls /dev/*ft*
> > /dev/ft0	/dev/ft0a	/dev/rft0	/dev/rft0a
> > sh-2.02# dd if=/dev/ft0 of=part1
> > dd: /dev/ft0: Operation not supported by device
> > 0+0 records in
> > 0+0 records out
> > 0 bytes transferred in 0.002494 secs (0 bytes/sec)
> > sh-2.02# dd if=/dev/ft0 of=part1^H^H^H^H^H^H^H^H^H^[[1@a
> > dd: /dev/ft0a: Operation not supported by device
> > 0+0 records in
> > 0+0 records out
> > 0 bytes transferred in 0.002441 secs (0 bytes/sec)
> > ^[[Ash-2.02# dd if=/dev/ft0a of=part1sh-2.02# ^[[Kdd if=/dev/ft0a of=part1^H^H^H^H^H^H^H^H^H^H^H^H^H^H/f^[[1@f^Hf^H^Hf^[[1P^H^[[1@rft0a^H^[[1P
> > dd: /dev/rft0: Operation not supported by device
> > 0+0 records in
> > 0+0 records out
> > 0 bytes transferred in 0.002512 secs (0 bytes/sec)
> > sh-2.02# dd if=/dev/rft0 of=part1^H^H^H^H^H^H^H^H^H^[[1@a
> > dd: /dev/rft0a: Operation not supported by device
> > 0+0 records in
> > 0+0 records out
> > 0 bytes transferred in 0.002448 secs (0 bytes/sec)
> > sh-2.02# 
> > sh-2.02# 
> > sh-2.02# ft
> > "Linux raw format V2" - Mon Apr 27 00:17:50 1998
> > sh-2.02# ft | dd if=- of=part1
> > dd: -: No such file or directory
> > Incorrect volume inserted.  This tape is:
> > "Linux raw format V2" - Mon Apr 27 00:17:50 1998
> > 
> > Insert ftfilt volume 01 and press enter:
> > ft: waiting for drive to become ready
> > ^C^C^C^C^C^C^C
> > sh-2.02# exit
> > 
> > Script done on Fri Oct  2 12:43:10 1998
> > 
> > 	 
> > 
> > On Fri, 2 Oct 1998, Thomas David Rivers wrote:
> > 
> > > > 
> > > > Hello.  I've read and been impressed by your FreeBSD propaganda and have
> > > > converted to your platform from Slackware Linux.
> > > > 	During the migration, I backed up all my serious data to QIC-80
> > > > tapes using tar.  Now when I try to retrieve the data, the ft filter
> > > > says that I've inserted the wrong volume and won't accept the
> > > > volume name of the Linux-generated tape.  How do I get around this?  The
> > > > data was a backup of an old operating system for my pdp11 and I can't
> > > > replace it, so it's critical.
> > > > 
> > > > thanks in advance
> > > > 
> > > > Jacob Ritorto
> > > > 
> > > > 
> > > > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > > > with "unsubscribe freebsd-questions" in the body of the message
> > > > 
> > > 
> > >  Jacob -
> > > 
> > > 	Did you do this with tar cvfM  and have multiple volumes?
> > > 
> > > 	If so, the problem you're reporting is caused by a bug in GNU tar.
> > > 	I've had it myself several times.  It seems to happen when a large
> > > 	file (larger than the block size) crosses a tape boundary.
> > > 
> > > 	Don't despair though - all of your data is there.  GNU tar has
> > > 	simply written too much on the second tape.
> > > 
> > > 	The solution I use is to simply dd the tape images.  Then with
> > > 	appropriate dd's, you can "chop off" the extra parts.
> > > 
> > > 	Another approach I've taken is to use pdtar (available in the usenet
> > > 	archives) which ignores GNU's multivolume stuff.   Then, you 
> > > 	can get the file which cross the boundary and put it back together
> > > 	appropriately (again, taking the "extra" stuff off of the front of
> > > 	the second half.)
> > > 
> > > 		- Dave Rivers -
> > > 
> > > 
> > 
> > 
> > 
> 
> 


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.01.9810021327090.2724-100000>