Re: tar: cannot open: /dev/rct0

From: Jean-Pierre Radley (jpr_at_jpr.com)
Date: 06/15/03 

Date: 15 Jun 2003 17:49:45 -0400

Doug Jarrett typed (on Sun, Jun 15, 2003 at 06:32:40PM +0000):
|
| I am having a problem with a series of identically configured Dell machines
| when I issue a specific tar command the first time after a fresh boot.
|
| Freshly booted machine.
| Log on to tty01 as root.
| Place a DAT tape in the drive and wait for at least 1 minute to insure that
| the tape drive is ready.
| Then enter the following command:
| # tar tv11 <enter>
|
| This produces the following error message:
|
| %Stp-0 - - - Vendor=ARCHIVE Product=Python 04106-XXX
| tar: cannot open: /dev/rct0
| #
|
| I can then issue the same tar command (tar tv11), and tar will execute as
| desired on the second attempt.
|
| Please Note: I do not have this problem when issuing "tar cv11
| /path_to_files" under the same circumstances.
|
| Any help is this matter will be greatly appreciated. Thanks for taking the
| time to read my post. Here are the particulars of the systems that I am
| having this problem on:
|
| Dell PowerEdge 600SC (Listed as SCO 5.0.6 Compatible)
| Seagate STD224000N-SB DAT Drive installed on Channel A of the onboard
| controller
| SCSI Hard Drive installed on Channel B of the onboard controller
| SCO 5.0.6 with Service Release 6a installed
|
| # All Rights Reserved.
| # The information in this file is provided for the exclusive use of
| # the licensees of The Santa Cruz Operation, Inc. Such users have the
| # right to use, modify, and incorporate this code into other products
| # for purposes authorized by the license agreement provided they include
| # this notice and the associated copyright notice with any such product.
| # The information in this file is provided "AS IS" without warranty.
| #
| # default/tar - archive devices: tar(C)
| #
| # device block size tape
| #
| archive0=/dev/rfd048ds9 18 360 n
| archive1=/dev/rfd148ds9 18 360 n
| archive2=/dev/rfd096ds15 10 1200 n
| archive3=/dev/rfd196ds15 10 1200 n
| # archive4=/dev/rfd096ds9 18 720 n
| archive4=/dev/rfd0135ds9 18 720 n
| archive5=/dev/rfd1135ds9 18 720 n
| # archive5=/dev/rfd196ds9 18 720 n
| archive6=/dev/rfd0135ds18 18 1440 n
| archive7=/dev/rfd1135ds18 18 1440 n
| archive8=/dev/rct0 20 0 y
| archive9=/dev/rctmini 20 0 y
| archive10=/dev/rdsk/fp03d 18 720 n
| archive11=/dev/rct0 20 12000000 y
| archive12=/dev/rdsk/fp03v21 10 20330 n

What were you trying to do when you created your own private entry 11?
Does entry 8 work OK? 

-- 
JP

Relevant Pages

  • Re: tar command
    ... that it executes upto the tar command but when it comes to the zip command ... or a combination of fork and exec. ...
    (perl.beginners)
  • Re: tar over 2 GB - how to backup it?
    ... I have seen cases of v5.1 tar being able to back up 10GB Oracle files ... 1.The tar command is not enabled for files greater than 2 Gig in size ... due to limitations imposed by XPG/4 and POSIX.2 standards. ...
    (comp.unix.aix)
  • tar: cannot open: /dev/rct0
    ... I am having a problem with a series of identically configured Dell machines ... when I issue a specific tar command the first time after a fresh boot. ... I can then issue the same tar command, ...
    (comp.unix.sco.misc)
  • tar: cannot open: /dev/rct0
    ... I am having a problem with a series of identically configured Dell machines ... when I issue a specific tar command the first time after a fresh boot. ... I can then issue the same tar command, ...
    (comp.unix.sco.misc)
  • Re: There is not enough memory available now.
    ... while i run tar command for backup a filesystems; ... I restore the tape data to other directory...but some file is lost ... the tar command uses a temporary file (the ... file) and maintains in memory a table of files with several links. ...
    (comp.unix.aix)