Tape Device files in Solaris 2.x

Tape Device files in Solaris 2.x

Post by Jim Levi » Fri, 13 Nov 1998 04:00:00



Quote:>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<


files in Solaris 2.x:

Quote:> I have a question concerning the device files and Solaris.  I have an
> UltraSparc 5 running Solaris 2.6 (with 5/98 hardware code).  We are
adding
> devices to the machine, in particular, SCSI disk and tape drives.  T
> When we add tape drives to the running system via the drvconfig
command and
> then run tapes, the /dev/rmt directory gets updated.  The problem that
we are
> seeing is if you remove a tape drive and add another device in it's
spot or
> add another tape device at another address.  After running the
drvconfig
> command again and running tapes, the old tape entries are still in the
> /dev/rmt/ directory.  A couple more times of doing this (we are
testing
> devices) and we get a bunch of entries to phantom tape drives in

/dev/rmt.

That's the way Solaris works... Kinda makes sense if you consider the
impacts that mutable tape assignments would have on backup scripts or
packages.

It's easy to fix. As root, just remove everything in /dev/rmt, touch
/reconfigure, and reboot. The currently connected devices will have
entries associated with them and all the old devices will be gone.

 
 
 

Tape Device files in Solaris 2.x

Post by Casper H.S. Dik - Network Security Engine » Fri, 13 Nov 1998 04:00:00


[[ PLEASE DON'T SEND ME EMAIL COPIES OF POSTINGS ]]


>When we add tape drives to the running system via the drvconfig command and
>then run tapes, the /dev/rmt directory gets updated.  The problem that we are
>seeing is if you remove a tape drive and add another device in it's spot or
>add another tape device at another address.  After running the drvconfig
>command again and running tapes, the old tape entries are still in the
>/dev/rmt/ directory.  A couple more times of doing this (we are testing
>devices) and we get a bunch of entries to phantom tape drives in /dev/rmt.

Device entries are not removed; the reason for this is mainly to prevent
conflicts.  E.g., if you remove a drive and add a new one under a different
ID, the system can't really tell whether you've just switched off the one
you've removed or that you've actually removed it.

Quote:>Our concern is that these entries are actually links back to the obfsucated
>device file paths and that they are pointing to device paths that might
>actually be pointing to nothing (or another type of device).  Someone might
>try and write to one of these bogus tape device paths and end sending data to
>another tape drive or worse yet, another device type.  At the least, having
>all of these phantom entries is downright confusing.

No.  There is no danger.  The device nodes will still exist but once you try
to access them you'll get a "no-such-device" error.

Quote:>Is there something that we are overlooking?  Is there a command or option that
>forces Solaris to remove device paths of devices that it no longer detects?  I
>know we can delete everything out of /dev/rmt and then run the tapes command,
>but that doesn't seem like a proper way of solving our problem.

There a reason for not cleaning the stuff up but I think this will be handled
better in future.

Casper
--
Expressed in this posting are my opinions.  They are in no way related
to opinions held by my employer, Sun Microsystems.
Statements on Sun products included here are not gospel and may
be fiction rather than truth.

 
 
 

Tape Device files in Solaris 2.x

Post by Dimitry Aliabie » Sat, 14 Nov 1998 04:00:00



>When we add tape drives to the running system via the drvconfig command and
>then run tapes, the /dev/rmt directory gets updated.  The problem that we are
>seeing is if you remove a tape drive and add another device in it's spot or
>add another tape device at another address.  After running the drvconfig
>command again and running tapes, the old tape entries are still in the
>/dev/rmt/ directory.  A couple more times of doing this (we are testing
>devices) and we get a bunch of entries to phantom tape drives in /dev/rmt.

What about devlinks after drvconfig ?

--

Best rgds,                      Dimitry

Network specialist              http://www.ucl.kiev.ua/~dimitry
Ukrainian Computer Laboratory   nic-hdl: DYA7-RIPE

 
 
 

1. dumping Solaris file system to Linux/Alpha tape device

Hi,

I'm trying to dump a file system from a Solaris 8 Sparc machine to
a tape device attached to a Linux/Alpha box. I'm using
  ufsdump 0f alpha:/dev/nst0 /
command which has always worked fine between Solaris machines.
First of all, I needed to make a link from /sbin/rmt to /etc
as Solaris ufsdump expects the remote "rmt" command on /etc.
Unfortunately this did not help much as I'm now getting:

  DUMP: rmtstatus: expected response size 24, got 48
  DUMP: This means the remote rmt daemon is not compatible.
  DUMP: Lost connection to remote host.

Strange. The "tar" command which AFAIK also uses "rmt" on the remote
host when the file (-f option) has "machine:/device" form, works
perfectly well in the very same environment.

I've found a workaround by redirecting usfdump output to stdout and
piping this to "rsh alpha dd ..." but still I wonder why it does not
work directly.

Any hints,

Michal.

--

  Warsaw University Observatory, Warszawa, POLAND

2. Installing Linux

3. Copy from tape device to tape device across the network

4. DSO Support in Apache

5. Porting tape device driver to Solaris 2.5

6. Weird - unlocked, clean and not uptodate buffer on list

7. Tape device handling (end of tape) in 2.4 / 2.6 problem

8. Lockup on named pipe operations under System V R4.

9. Raw char devices + tar file on 1 tape

10. Tricking Unix into thinking a a Unix file is actually a tape device

11. backing up to remote tape device on Solaris

12. tar segfaults reading remote tape device based on TAPE variable

13. how to mount a tape device on a Sun Solaris 1.1