09-09-2008
Is there some read notch on side or back. Check if it is the cause that has made the tape read-only ....
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi,
I' using a sun solaris server, I would like to known if there is the possibility to control how many space is free on a tape and how I can delete a single file on a tape.
Thanks
DOMENICO (3 Replies)
Discussion started by: Minguccio75
3 Replies
2. UNIX for Dummies Questions & Answers
Hi there: I'm new here
Can anyone help me:
I have DS15 Alpha server : Unix 5.1B
Now i need to connect a DLVT VS80 1U Rackmount Tape Drive unit.
What is the exact comman to mount the DLTape IV??
How do i make backuo @ copy file to the tape?
Thanx to all (0 Replies)
Discussion started by: ayzeayem
0 Replies
3. SCO
when I do a tape status /dev/rStp0 I get the following on a new tape and I have tried several:
Status : ready beginning-of-tape
soft errors : 0
hard errors: 2
underruns: 5
My BackupEdge has stopped backing up my system because it asks for a new volume yet my total system data is under 20... (5 Replies)
Discussion started by: psytropic
5 Replies
4. Solaris
Hello Guruz,
Relay bad condition :mad:
Some has changed the permission to 777 recursively for /usr/bin directory by mistake. Now all the permission looks to be 777 on /usr/bin
Hence I am so many system related errors as 1 show below.
When I am trying to change the password, I am getting... (5 Replies)
Discussion started by: bullz26
5 Replies
5. OS X (Apple)
I accidentally changed to sudo chmod a=w to my /usr/bin folder on my macbook with OS 10.5.8... Please help! I can't even get into a terminal correctly cause it displays:
-bash: uname: command not found
-bash: cut: command not found
-bash: uname: command not found
-bash: cut: command not found... (6 Replies)
Discussion started by: scaryMac23
6 Replies
6. UNIX for Dummies Questions & Answers
Can any one tell me is there any command to find out who changed the permission of a file Or is there any log file so that i can find out who has changed the permission of a file?
Thanks in Advance:) (7 Replies)
Discussion started by: Uttamnsd
7 Replies
7. HP-UX
HI all,
We had created new user using the command useradd -d /home/selva -s /usr/local/bin/bash selva. But it didnt created the home directory on /home. So i manually created, copied skel files manually and changed the owner from root to selva. At the same time i observed that so many files... (6 Replies)
Discussion started by: selvaforum
6 Replies
8. AIX
Friends,
I've tried to modify the syslogs permission by using the perm option in the syslog configuration in AIX 6.1 TL 05. But its not getting applied after the configuration. Have restarted the syslog service also.
Need your help!:wall:
The below are the conf details and os versions
>... (1 Reply)
Discussion started by: novaothers
1 Replies
9. Shell Programming and Scripting
Hi All,
I have to work in the late nights some times for server maintenance and in a hurry to complete I am accidentally changing ownership or permission of directories :(
which have similar names ( /var in root and var of some other directory ).:confused:
Can some one suggest me with the... (1 Reply)
Discussion started by: shiek.kaleem
1 Replies
10. Linux
Hello everybody,
I have many mount points on my virtual Redhat server, two of them lost their (write) permission, so they became read-only filesystems.
I fixed this problem.
But I want to know why it happened? What is the reason behind that to avoid it again? Where can I find related logs?... (2 Replies)
Discussion started by: Mohannad
2 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)