Date: Wed, 12 Jun 1996 13:10:00 -0700 (PDT) From: Doug White <dwhite@riley-net170-164.uoregon.edu> To: Eric Chan <Eric.Chan@nswcc.org.au> Cc: questions@FreeBSD.ORG Subject: Re: your mail Message-ID: <Pine.BSF.3.91.960612124430.7312B-100000@riley-net170-164.uoregon.edu> In-Reply-To: <199606120215.MAA13798@moredun.nswcc.org.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 12 Jun 1996, Eric Chan wrote:
> I was doing the file system backup using dump command to the tape on
> other machine across the network. But it was not running smoothly.
We fought this too, and won :-)
> TCP_MAXSEG setsockopt: Invalid argument
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> What is that? How to fix it...?
I think we get this if we don't run as root.
Can you send over your command line?
> DUMP: Date of this level 0 dump: Tue Jun 11 16:53:01 1996
> DUMP: Date of last level 0 dump: the epoch
> DUMP: Dumping /dev/rsd0a (/) to /dev/nrmt0h on host styx
> DUMP: mapping (Pass I) [regular files]
> DUMP: mapping (Pass II) [directories]
> DUMP: estimated 13966 tape blocks on 0.36 tape(s).
> DUMP: dumping (Pass III) [directories]
> DUMP: dumping (Pass IV) [regular files]
> DUMP: DUMP: 13961 tape blocks on 1 volumes(s)
That is a tiny tape or a huge blocksize.
> DUMP: level 0 dump on Tue Jun 11 16:53:01 1996
> DUMP: Closing /dev/nrmt0h
> DUMP: DUMP IS DONE
Well, that one worked.
> TCP_MAXSEG setsockopt: Invalid argument
> DUMP: Date of this level 0 dump: Tue Jun 11 16:53:59 1996
> DUMP: Date of last level 0 dump: the epoch
> DUMP: Dumping /dev/rsd0e (/usr) to /dev/nrmt0h on host styx
> DUMP: mapping (Pass I) [regular files]
> DUMP: mapping (Pass II) [directories]
> DUMP: estimated 96050 tape blocks on 2.47 tape(s).
> DUMP: dumping (Pass III) [directories]
> DUMP: dumping (Pass IV) [regular files]
> DUMP: Closing /dev/nrmt0h
> DUMP: Change Volumes: Mount volume #2
> DUMP: fopen on /dev/tty fails: Device not configured
> DUMP: The ENTIRE dump is aborted.
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> What is that and how to fix it...?
Your command line is probably wrong. Why on earth it wants to open
/dev/tty is beyond me.
This is how our command lines look:
rdump 0uBbf 2000000 10 resnet2.uoregon.edu:/dev/nrst0 /
rdump 0uBbf 2000000 10 resnet2.uoregon.edu:/dev/nrst0 /var
rdump 0uBbf 2000000 10 resnet2.uoregon.edu:/dev/nrst0 /usr
rdump 0uBbf 2000000 10 resnet2.uoregon.edu:/dev/rst0 /usr1
^^ I think the key is here
We're using a Connor TapeStor 4000(?) SCSI tape with 2GB QIC3020 tapes.
Doug White | University of Oregon
Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant
http://gladstone.uoregon.edu/~dwhite | Computer Science Major
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.91.960612124430.7312B-100000>