- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Re: Unable to verify data on DDS-3
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-11-2008 11:54 PM
тАО07-11-2008 11:54 PM
This morning after backup I have run command:
tar tvf /dev/rmt0h
Receive error:
tar: [offset 0]: No space left on device
Any ideas as to what might be causing this and what I can do to resolve?
Many Thanks,
Phil.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-12-2008 02:55 AM
тАО07-12-2008 02:55 AM
Re: Unable to verify data on DDS-3
I wouldn't normally expect to see a "No space" error when reading data from a tape...
However your previous posts show that you've swapped tape drives recently. I'll take a guess that at some point a backup has been done pointing to a /dev/rmt... device that doesn't exist, which has consequently filled up the root file system.
Does the output of "df -k" show any filesystems at 100% ?
Cheers,
Rob
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-12-2008 04:00 AM
тАО07-12-2008 04:00 AM
Re: Unable to verify data on DDS-3
You are correct regards previous backup. I would have thought the new drive would have the same lable rmt0h? Is this not the case? I did a backup on Thursday with the new device and all was OK (different type of backup)?
More of a windows man myself!!
What could I do to resolve?
Many Thanks,
Phil.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-12-2008 01:10 PM
тАО07-12-2008 01:10 PM
Re: Unable to verify data on DDS-3
run dsfmgr -k
this will add device file for newly added tape drive and then use new device file to take backup.(ls -lrt /dev last files would be newly created one).
BR,
Kapil
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-13-2008 01:45 AM
тАО07-13-2008 01:45 AM
Re: Unable to verify data on DDS-3
dsfmgr: not found
Regards,
Phil.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-13-2008 02:16 AM
тАО07-13-2008 02:16 AM
Re: Unable to verify data on DDS-3
Extract from daily backup script (not written by me) as follows:
[code]
RECOVERY=/appdb/recovery.log; export RECOVERY
TAPEDRIVE=/dev/rmt0h; export TAPEDRIVE
APPDBDIR=/appdb; export APPDBDIR
APPDBRECOVERY=/appdb; export APPDBRECOVERY
APPDIR=/app; export APPDIR
# Stop the BSCqueu.run routine (to free up RECOVERY), if it is running
#
echo `date` " Start of CRON processing"
/app/bin/AUTOBACKUP
echo `date` " End of CRON processing"
[/code]
The daily backup calls script AUTOBACKUP as follows:
[code]
set +x
#
# app Shell Command Script to renew the "RECOVERY.LOG"
# file in /appdb/ after a backup has been made.
#
# VERSION 9.1.2.1 - DBBACKUP 91/10/10 10:32:36
# !!!!! WARNING - date statement uses sccs format
# DO NOT USE GET (Use GETEDIT or Maintain manually)
msg1="app Users on System - Can not Proceed."
there=`ps -ae | grep -c "dbh010.r"`
if [ $there -gt 1 ]
then
clear
echo " "
echo $msg1
mail root < /app/bin/BACKUP_FAIL
echo " "
exit
fi
date=`date +%m%d%H%M`
RECOVERY_SAVE=$appDBRECOVERY/LOG$date.LOG
echo "\f\fapp backup procedure: $RECOVERY renewal"
echo "Recovery file $RECOVERY will be moved to $RECOVERY_SAVE"
#echo "\nConfirm Backup of Database and replacement of '$RECOVERY' : \c"
confirm=YES
#read confirm
there=`ps -ae | grep -c "dbh010.r"`
if [ $there -gt 1 ]
then
clear
echo " "
echo $msg1
mail root < /app/bin/BACKUP_FAIL
echo " "
exit
fi
case $confirm in
y|Y|yes|YES)
if test -r $RECOVERY
then
touch $appDIR/tmp/dbh.lock
cd /appdb1
tar cvB -C /appdb1 . -C /appdb2/appdb1 .
# find DS*.* -print | cpio -ocBvdum > $TAPEDRIVE
# Following added by KH to check for unsuccessful backup to tape
if [ $? = 0 ]
then
echo "\nBackup Successful \n"
mail root < /app/bin/TAPE_SUCCESS
else
echo "\nBackup Failed \n"
mail root < /app/bin/TAPE_FAIL
# exit
fi
# KH - end
mv $RECOVERY $RECOVERY_SAVE
if [ $? = 0 ]
then
echo "\nPrevious $RECOVERY now in $RECOVERY_SAVE\n"
touch $RECOVERY
chmod 777 $RECOVERY
chown appadm $RECOVERY
chgrp app $RECOVERY
rm $appDIR/tmp/dbh.lock
echo " \nNew $RECOVERY now created\n"
echo "\nBackup of Database Complete ..You May Resume Normal app operations now .\n"
mail root < /app/bin/BACKUP_SUCCESS
else
echo "\nUnable to copy $RECOVERY into $RECOVERY_SAVE\n"
rm $appDIR/tmp/dbh.lock
exit
fi
else
echo "\nUnable to find $RECOVERY \n"
mail root < BACKUP_FAIL
exit
fi
;;
n|N|NO|no)
echo "No action taken"
echo "\nDATABASE NOT BACKED UP !!!!!\n\007\007\007"
;;
esac
[/code]
Any help very much appreciated.
Phil.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-14-2008 12:06 AM
тАО07-14-2008 12:06 AM
Re: Unable to verify data on DDS-3
did you check the scsi-id on the drive matches id-0 (rmt0 )!
or did you now create an rmt1 !
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-14-2008 02:24 AM
тАО07-14-2008 02:24 AM
Re: Unable to verify data on DDS-3
[link] http://forums12.itrc.hp.com/service/forums/questionanswer.do?threadId=1248318&admit=109447627+1216030720135+28353475
[/link]
scu show edt lists device as:
Bus: 0, Target:1, Lun:0, Type: Sequential Access
My boot file lists device as:
tz1 at scsi0 target 1 lun 0 (LID=0) (compaq SDT-9000)
Just ran: file /dev/nrmt0h
This has returned:
/dev/nrmt0h: character special (9/1027) SCSI #0 SDT-9000 tape #0 (SCSI ID #1) (SCSI LUN #0) offline
Can you assist?
Many Thanks,
Phil.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-14-2008 02:37 AM
тАО07-14-2008 02:37 AM
Re: Unable to verify data on DDS-3
/dev/nrmt0h online 1 failed: I/O error
Kind Regards,
Phil.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-14-2008 02:45 AM
тАО07-14-2008 02:45 AM
Re: Unable to verify data on DDS-3
looks like you're writing to a directory.
>>> cd /appdb1
>>> tar cvB -C /appdb1 . -C /appdb2/appdb1 .
also looks lik the os can reach the tapeunit, but the device is off-line.
with DLT drives after loading the tape you must put the unit-online. I don't think the SDT-900 has such a button.
try if if "mt online" command works on this version (we don't have V4.0 anymore so i can't test; mt - Magnetic tape manipulating program)