Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Failed to open tape device /dev/rmt/0mn:Device busy (errno = 16)
Operating Systems HP-UX Failed to open tape device /dev/rmt/0mn:Device busy (errno = 16) Post 302971742 by anuragr on Monday 25th of April 2016 07:04:40 AM
Old 04-25-2016
Failed to open tape device /dev/rmt/0mn:Device busy (errno = 16)
Hi,

Unable to make tape backup, please help.

Code:
/opt/ignite/bin/make_tape_recovery -a /dev/rmt/?mn -I -v -m tar -x inc_entire=vg00

 * Creating local directories for configuration files and archive.

=======  04/25/16 16:28:08 IST  Started /opt/ignite/bin/make_tape_recovery.
         (Mon Apr 25 16:28:08 IST 2016)
         @(#)Ignite-UX Revision C.7.5.142
         @(#)ignite/net_recovery (opt) Revision:
         /branches/IUX_RA0803/ignite/src@72866 Last Modified: 2008-02-06
         15:49:50 -0700 (Wed, 06 Feb 2008)

       * Testing for necessary pax patch.
       * Recovery Archive Description = Recovery Archive

       * Recovery Archive Location    = /dev/rmt/0mn

       * Number of Archives to Save   = 2

       * Pax type  = tar


        In?     dsk/vg  name                    minor#  Associated disks/mountpoints
        2       v       /dev/vg00               0x00    /dev/disk/disk3_p2
                                                /dev/vg00/lvol1 /stand  2
                                                /dev/vg00/lvol2
                                                /dev/vg00/lvol3 /       2
                                                /dev/vg00/lvol4 /home   2
                                                /dev/vg00/lvol5 /opt    2
                                                /dev/vg00/lvol6 /soft   2
                                                /dev/vg00/lvol7 /tmp    2
                                                /dev/vg00/lvol8 /usr    2
                                                /dev/vg00/lvol9 /var    2

        ** 0 - The Volume Group or Filesystem is Not included in the
               System Recovery Archive
        ** 1 - The Volume Group or Filesystem is Partially included in the
               System Recovery Archive
        ** 2 - The Volume Group or Filesystem is Fully included in the
               System Recovery Archive

       * Checking Versions of Ignite-UX filesets
ERROR:   Failed to open tape device /dev/rmt/0mn:Device busy (errno = 16).
ERROR:   Check tape device failed.

=======  04/25/16 16:28:09 IST  make_tape_recovery completed unsuccessfully

>ioscan -funC tape
Class     I  H/W Path     Driver S/W State   H/W Type     Description
=====================================================================
tape      0  0/4/1/0.0.0  stape   CLAIMED     DEVICE       HP      Ultrium 3-SCSI
                         /dev/rmt/0m            /dev/rmt/0mnb          /dev/rmt/c1t0d0BESTn
                         /dev/rmt/0mb           /dev/rmt/c1t0d0BEST    /dev/rmt/c1t0d0BESTnb
                         /dev/rmt/0mn           /dev/rmt/c1t0d0BESTb

>fuser -u /dev/rmt/0m*
/dev/rmt/0m:
/dev/rmt/0mb:
/dev/rmt/0mn:     7701o(root)
/dev/rmt/0mnb:

>ps -ef |grep 7701
    root  6855 21540  0 16:30:58 pts/0     0:00 grep 7701
    root  7701     1  0  Apr 23  pts/0    10:15 /sbin/pax -dwx ustar -f /dev/rmt/0mn


>kill -9 7701

>kill -9 7701

>ps -ef |grep 7701
    root  7701     1  0  Apr 23  pts/0    10:15 /sbin/pax -dwx ustar -f /dev/rmt/0mn
    root  7127 21540  0 16:31:25 pts/0     0:00 grep 7701

>mt -f /dev/rmt/0m status
on tape open: Device busy

>mt -f /dev/rmt/0m rew
/dev/rmt/0m: Device busy

 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

"/dev/rmt/0: No such device or address" when using mt command

/dev/rmt/0: No such device or address I get this when I do a "mt -f /dev/rmt/0 rewind" This is on a Solaris 7 system. I tried devfsadm -c tape and drvconfig ; tape and both didn't work. Help please....... :confused: (4 Replies)
Discussion started by: shorty
4 Replies

2. UNIX for Dummies Questions & Answers

mt command shows /dev/tape: inappropriate ioctl for device

Hello guys, on my Red Hat machine the /bin/mt status command gives the output dev/tape: inappropriate ioctl for device. This messages comes up after the Server has been rebooted. Anybody an idea? Thx masterofdesaster (8 Replies)
Discussion started by: masterofdesaste
8 Replies

3. UNIX Desktop Questions & Answers

cygwin /dev/ttyS2: Device or resource busy

Ciao a tutti!!! il mio problema è questo: sto cercando di inviare dei comandi AT da PC a cellulare utilizzando il bluetooth e cygwin e vorrei visualizzare le risposte nella shell bash. Per farlo apro due terminali utilizzando le seguente istruzioni: xterm & Sul primo scrivo cat /dev/ttyS2 ... (0 Replies)
Discussion started by: blianna
0 Replies

4. UNIX and Linux Applications

/dev/ttyS2 device or resource busy

Ciao a tutti!!! il mio problema è questo: sto cercando di inviare dei comandi AT da PC a cellulare utilizzando il bluetooth e cygwin e vorrei visualizzare le risposte nella shell bash. Per farlo apro due terminali utilizzando le seguente istruzioni: xterm & Sul primo scrivo cat /dev/ttyS2 ... (1 Reply)
Discussion started by: blianna
1 Replies

5. SuSE

Tape Loader Device /dev/sgN is altering after each reboot

Dear all, we are running SLES 11 where an iscsi tape library is attached. To load the tape in a slot we are using for instance the command #mtx -f /dev/sg1 load 2 which is doing very well. But after a server's reboot the device name of the loader is now /dev/sg4 or /dev/sg5 I mean it is... (1 Reply)
Discussion started by: xunil321
1 Replies

6. Solaris

/dev/rmt is empty - Trying to make Tape Drive Functional

I have an HP Proliant DL380 with Intel Processors that I recently loaded Solaris 10 with latest patches on it. I'm trying to do a ufsdump to an HP DAT 40 tape drive via SCSI, but I can't get it to do anything because /dev/rmt is empty. I've tried the following with luck: touch /reconfigure,... (7 Replies)
Discussion started by: cvaughn
7 Replies

7. Hardware

/dev/rmt/0mn: write protected or reserved

# mt stat HP DDS-4 DAT (Sun) tape drive: sense key(0x0)= No Additional Sense residual= 0 retries= 0 file no= 0 block no= 0 mt -f /dev/rmt/0mn erase /dev/rmt/0mn: write protected or reserved. Getting error while ufsdump .... --- Dumping / to /dev/rmt/0mn --- DUMP: Date... (1 Reply)
Discussion started by: vickyingle5
1 Replies

8. Solaris

/dev/rmt/0mn: write protected or reserved

# mt stat HP DDS-4 DAT (Sun) tape drive: sense key(0x0)= No Additional Sense residual= 0 retries= 0 file no= 0 block no= 0 mt -f /dev/rmt/0mn erase /dev/rmt/0mn: write protected or reserved. Getting error while ufsdump .... --- Dumping / to /dev/rmt/0mn --- DUMP: Date... (5 Replies)
Discussion started by: vickyingle5
5 Replies

9. Hardware

/dev/ttyS0: Device or resource busy

hello to everybody I have Ubuntu Lucid 10.04 installed on my Desktop and I have a PCI serial card in my computer and it has only one serial port. Actually I want to use this serial port for the serial communication and for that I executed this command : $ setserial -g /dev/ttyS and I... (0 Replies)
Discussion started by: piyush011
0 Replies

10. UNIX for Advanced & Expert Users

lvm swapon failed Device or resource busy

Is there a trick to mounting swap in n a lvm? I can't get it to work. # swapon -va swapon on /dev/mapper/VG-lv_swap swapon: /dev/mapper/VG-lv_swap: found swap signature: version 1, page-size 4, same byte order swapon: /dev/mapper/VG-lv_swap: pagesize=4096, swapsize=4294967296,... (1 Reply)
Discussion started by: cokedude
1 Replies

LEARN ABOUT OPENSOLARIS

device_maps

device_maps(4)							   File Formats 						    device_maps(4)

NAME

       device_maps - device_maps file

SYNOPSIS

       /etc/security/device_maps

DESCRIPTION

       The  device_maps file contains access control information about each physical device. Each device is represented by a one line entry of the
       form:

	 device-name : device-type : device-list :

       where

       device-name

	   This is an arbitrary ASCII string naming the physical device. This field contains no embedded white space or non-printable characters.

       device-type

	   This is an arbitrary ASCII string naming the generic device type. This field identifies and groups together devices of like type.  This
	   field contains no embedded white space or non-printable characters.

       device-list

	   This  is  a	list  of  the device special files associated with the physical device. This field contains valid device special file path
	   names separated by white space.

       The device_maps file is an ASCII file that resides in the /etc/security directory.

       Lines in device_maps can end with a `' to continue an entry on the next line.

       Comments may also be included. A `#' makes a comment of all further text until the next NEWLINE not immediately preceded by a `'.

       Leading and trailing blanks are allowed in any of the fields.

       The device_maps file must be created by the system administrator before device allocation is enabled.

       This file is owned by root, with a group of sys, and a mode of 0644.

EXAMPLES

       Example 1 A Sample device_maps File

       The following is a sample device_maps file:

	 # scsi tape
	 st1:
	 rmt:
	 /dev/rst21 /dev/nrst21 /dev/rst5 /dev/nrst5 /dev/rst13 
	 /dev/nrst13 /dev/rst29 /dev/nrst29 /dev/rmt/1l /dev/rmt/1m 
	 /dev/rmt/1 /dev/rmt/1h /dev/rmt/1u /dev/rmt/1ln /dev/rmt/1mn 
	 /dev/rmt/1n /dev/rmt/1hn /dev/rmt/1un /dev/rmt/1b /dev/rmt/1bn:

FILES

       /etc/security/device_maps    Contains access control information for devices.

ATTRIBUTES

       See attributes(5) for descriptions of the following attributes:

       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Interface Stability	     |Uncommitted		   |
       +-----------------------------+-----------------------------+

SEE ALSO

       allocate(1), bsmconv(1M), deallocate(1), list_devices(1), dminfo(1M), device_allocate(4), attributes(5)

NOTES

       The functionality described in this man page is available only if  Solaris Auditing has been enabled. See bsmconv(1M) for more information.

       On systems configured with Trusted Extensions, the functionality is enabled by default. On such systems,  the  device_allocate(4)  file	is
       updated automatically by the system.

SunOS 5.11							    30 Apr 2008 						    device_maps(4)
All times are GMT -4. The time now is 10:28 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy