11-12-2010
"rmt0" is not a valid backing device - VIO
hello to all,
i am trying to assing a tape drive to a virtual partition through VIO but i get the message "rmt0" is not a valid backing device.
the oslevel of my VIO is AIX 6.1.3.0. when i run the command
lsdev |grep rmt i get the following result:
rmt0 Available 08-08-00-0,0 Other SCSI Tape Drive
the problem is when i use the command mkvdev to assign the tape drive to the virtual partition. the command i use is the following:
mkvdev -vdev rmt0 -vadapter vhost3 -dev LTO4
when i run this command i get the message mentioned above.
also i check the entry in the ODM for the rmt and i when i run then command odmget CuDv i get the following result:
CuDv:
name = "rmt0"
status = 1
chgstatus = 0
ddins = "tape"
location = "08-08-00-0,0"
parent = "scsi0"
connwhere = "0,0"
PdDvLn = "tape/scsi/ost"
i find the the status=1 means that the device is defined. so is there a way to change the status of the device in the ODM database and if i can, does this fix the problem that i face?
if it is helpful the AIX version of my virtual partition is 5.3.0.0
thank you for your time
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi Friends,
Can any of you explain me about the below line of code?
mn_code=`env|grep "..mn"|awk -F"=" '{print $2}'`
Im not able to understand, what exactly it is doing :confused:
Any help would be useful for me.
Lokesha (4 Replies)
Discussion started by: Lokesha
4 Replies
2. Emergency UNIX and Linux Support
Dear All,
I was having powerpath 5.2 on SUN server with SVM connected to CLARIION box.Please find the following output :
root # powermt display dev=all
Pseudo name=emcpower3a
CLARiiON ID=CK200073400372
Logical device ID=60060160685D1E004DD97FB647BFDC11
state=alive; policy=CLAROpt;... (1 Reply)
Discussion started by: Reboot
1 Replies
3. Shell Programming and Scripting
Hi,
I have line in input file as below:
3G_CENTRAL;INDONESIA_(M)_TELKOMSEL;SPECIAL_WORLD_GRP_7_FA_2_TELKOMSEL
My expected output for line in the file must be :
"1-Radon1-cMOC_deg"|"LDIndex"|"3G_CENTRAL|INDONESIA_(M)_TELKOMSEL"|LAST|"SPECIAL_WORLD_GRP_7_FA_2_TELKOMSEL"
Can someone... (7 Replies)
Discussion started by: shis100
7 Replies
4. Shell Programming and Scripting
Hi, im asking for help with the next script:
echo ^;
then
if
then
printf "\033
query1.sh:
export TERM=vt100
export ORACLE_TERM=at386
export ORACLE_HOME=/home_oracle8i/app/oracle/product/8.1.7
export ORACLE_BASE=/home_oracle8i/app/oracle
export... (8 Replies)
Discussion started by: blacksteel1988
8 Replies
5. AIX
Dear all
First of all, my English not so good.
We have p52a (production server) and p52a (test server). Tape drives are VXA2.
When both servers were AIX 5.3, mksysb on production server and restoring to test server was OK.
The production server was AIX 5.3 and recently upgraded to... (3 Replies)
Discussion started by: fifa15pc
3 Replies
6. UNIX for Dummies Questions & Answers
How to use "mailx" command to do e-mail reading the input file containing email address, where column 1 has name and column 2 containing “To” e-mail address
and column 3 contains “cc” e-mail address to include with same email.
Sample input file, email.txt
Below is an sample code where... (2 Replies)
Discussion started by: asjaiswal
2 Replies
7. Shell Programming and Scripting
Hello.
System : opensuse leap 42.3
I have a bash script that build a text file.
I would like the last command doing :
print_cmd -o page-left=43 -o page-right=22 -o page-top=28 -o page-bottom=43 -o font=LatinModernMono12:regular:9 some_file.txt
where :
print_cmd ::= some printing... (1 Reply)
Discussion started by: jcdole
1 Replies
8. AIX
Hi 2 all,
i have had AIX 7.2
:/# /usr/IBMAHS/bin/apachectl -v
Server version: Apache/2.4.12 (Unix)
Server built: May 25 2015 04:58:27
:/#:/# /usr/IBMAHS/bin/apachectl -M
Loaded Modules:
core_module (static)
so_module (static)
http_module (static)
mpm_worker_module (static)
... (3 Replies)
Discussion started by: penchev
3 Replies
HT(4) Kernel Interfaces Manual HT(4)
NAME
ht - RH-11/TU-16 magtape interface
DESCRIPTION
The files mt0, mt1, ... refer to the DEC RH/TM/TU16 magtape. When opened for reading or writing, the tape is not rewound. When closed,
it is rewound (unless the 0200 bit is on, see below). If the tape was open for writing, a double end-of-file is written. If the tape is
not to be rewound the tape is backspaced to just between the two tapemarks.
A standard tape consists of a series of 512 byte records terminated by a double end-of-file. To the extent possible, the system makes it
possible, if inefficient, to treat the tape like any other file. Seeks have their usual meaning and it is possible to read or write a byte
at a time. Writing in very small units is inadvisable, however, because it tends to create monstrous record gaps.
The last octal digit of the minor device number selects the drive. The middle digit selects a controller. The initial digit is even to
select 800 BPI, odd to select 1600 BPI. If the 0200 bit is on (initial digit 2 or 3), the tape is not rewound on close. Note that the
minor device number has no necessary connection with the file name, and in fact tp(1) turns the short name x into `/dev/mtx'.
The mt files discussed above are useful when it is desired to access the tape in a way compatible with ordinary files. When foreign tapes
are to be dealt with, and especially when long records are to be read or written, the `raw' interface is appropriate. The associated files
may be named rmt0, ..., rmt7, but the same minor-device considerations as for the regular files still apply.
Each read or write call reads or writes the next record on the tape. In the write case the record has the same length as the buffer given.
During a read, the record size is passed back as the number of bytes read, provided it is no greater than the buffer size; if the record is
long, an error is indicated. In raw tape I/O, the buffer must begin on a word boundary and the count must be even. Seeks are ignored. A
zero count is returned when a tape mark is read; another read will fetch the first record of the next tape file.
FILES
/dev/mt?, /dev/rmt?
SEE ALSO
tp(1)
BUGS
The magtape system is supposed to be able to take 64 drives. Such addressing has never been tried.
Taking a drive off line, or running off the end of tape, while writing have been known to hang the system.
If any non-data error is encountered, it refuses to do anything more until closed. In raw I/O, there should be a way to perform forward
and backward record and file spacing and to write an EOF mark explicitly.
HT(4)