[Can't open /dev/tty to prompt for more media]

[Eric Antunes]

STM:

The above post was about "information" about the tape drive.



I'm not able to diagnose:

-- Diagnose Information Log for SCSI Tape on path 0/7/0/0.3.0 --

Version A.01.02

This program may only be used by HP support personnel and those customers with
the appropriate Class license for systems specified by the license. HP shall
not be liable for any damages resulting from misuse or unauthorized use of this
program. This program remains the property of HP.


The SCSI DLT diagnose tool (diag_dlt) is intended to diagnose suspect DLT tape
drives and isolate faults at the FRU level. Three different levels of testing
are available:

Minimum Coverage - Performs Level 1 Electronics Self-Test.
This test is intended to provide a quick check
of the drive electronics to determine if the basic
mechanism is functional.
(Duration: 5 seconds per iteration)

Medium Coverage - Performs Level 1 Electronics Self-Test plus
Level 2 Write/Read Functionality Self-Test.
This test is intended to provide a thorough check
of the main components of the drive mechanism
within a reasonable amount of time.
(Duration: 5 minutes per iteration)

Maximum Coverage - Performs Level 1 Electronics Self-Test plus
Level 2 Write/Read Functionality Self-Test plus
Maximum coverage also performs error rate checking.
Error rate checking is performed by writing and
reading 1GB of random data to the tape. Then the
write and read error counter logs are checked.
If the error count is greater than the allowed
threshold (2000 for writes and 500 for reads),
then the error rate test reports a failure.
(Duration: 30 minutes per iteration)



The following is "current device status":

-- Current Device Status Log for SCSI Tape on path 0/7/0/0.3.0 --

The following information was archived during the last hardware scan:

Product : SCSI Tape
Qualifier : QUANTUMDLT8000
Hardware Path : 0/7/0/0.3.0
Device Type : Tape
Device Qualifier : DLT

Most Recent Tool Run : Information
Tool Exit Status : Success
Current Status : Success

Recommended Action : None

Installed tools:
Diagnostic : diag_dlt (Licensed)
Verifier : tape
Exerciser : tape
Information : scsi_dlt
Expert Tool : scsi_dlt (Licensed)
Firmware Update : scsi_tape

[Victor BERRIDGE]

I woulnd limit for cron/backup purpose....
well since you have a hardware issue I dont know if it is the cause...
But if you want to try by setting ulimit to unlimited then :
ulimit -c unlimited;

You can always give it a try...

My 2 cents
All the best
Victor

[Victor BERRIDGE]

Fool me...
ulimit [-HSacdfnst] [limit]

Set or display a resource limit. The limit for a specified
resource is set when limit is specified. The value of limit can
be a number in the unit specified with each resource, or the
keyword unlimited.

The -H and -S flags specify whether the hard limit or the soft
limit is set for the given resource. A hard limit cannot be
increased once it is set. A soft limit can be increased up to
the hard limit. If neither -H nor -S is specified, the limit
applies to both. The current resource limit is printed when
limit is omitted. In this case, the soft limit is printed unless
-H is specified. When more than one resource is specified, the
limit name and unit are printed before the value.

If no option is given, -f is assumed.

-a List all of the current resource limits.
-c The number of 512-byte blocks in the size of core
dumps.

-d The number of kilobytes in the size of the data area.
-f The number of 512-byte blocks in files written by child
processes (files of any size can be read).
-n The number of file descriptors.
-s The number of kilobytes in the size of the stack area.
-t The number of seconds to be used by each process.



from man sh-posix...

All the best
Victor

[Eric Antunes]

Victor,


I've tried this morning the cron job putting the command "tar cvf /dev/rmt/0m -C " and it worked fine. Now I'm going to try with your suggestion. You are saying to try with:

ulimit -f unlimited;

Is it correct?

[Eric Antunes]

I forgotted to say that now I'm going to try it using the script.sh I was using before (I think this errors began since I'm usind this script instead of putting the command directly on SAM)...

[Eric Antunes]

Ok, the cron backup job is working fine now that I put the tar command directly on SAM.

Thanks,

Eric