11-22-2000
Thanks for the man page pointer. Here are my current thoughts of what I would do if this was my problem and some background discussion.
First of all, in my years of HPUX experience, I always tried to avoid using SAM. SAM does many commands when you execute a function and it is hard to debug errors, as you are discovering.
Back away from SAM, decide what you are going to do, use the HP documentation and man pages and do it, step-by-step without SAM in between you and the environment. This has always been my method-of-operating in an HPUX environment. That is not to say that SAM is 'not good' because I use it to add users, groups and other less complex tasks. However,
for non-trivial tasks or tasks that are giving errors, I immediately move from SAM to the command line.
Now, assume you are at the command line. Take a look at the files and their permissions, write them down, etc. Start your reconfiguration step-by-step. If that does not work and you get errors, for example with frecover(); I would use a system call tracing utility to find out what is the exact HPUX system call returning the error and the arguments being passed to the system call. Sometimes the return codes of the systems call are much more informative that the text messages in the console. You will have to read the detailed man pages of the system calls to get this information. Somethings you will have to go into the header files in the associated system libs and look for the #defines in the right includes to get the next level of details.
I don't recall the name of the HPUX system call trace utility, something like ptrace() or strace() or something like that. There is one however, and learning to use it will become one of your greatest sysadmin debugging tools.
However, in many cases, just executing the task from the command line, step-by-step, in a controlled manner, with lead to a discovery of the problem. It may not be necessary to go a level deeper into system call tracing; but you will surely learn a lot about your environment getting out from under SAM and into the nuts-and-bolts of the task at hand.
6 More Discussions You Might Find Interesting
1. HP-UX
I have machine (HP-UX) 11.x and I took backup using fbackup (took 4 DDS tapes) then i did restore using frecover . the restore
failed on the 4th tape . and the process killed .
Can I restore only the 4th tape. or I have to do full recover from biginning ? (1 Reply)
Discussion started by: salhoub
1 Replies
2. UNIX for Dummies Questions & Answers
Hi,
Can someone please explain how I can check whether my files were backed-up to tape.
I issued this command and got an error:-
# frecover -I /tmp/mth -f /dev/rmt/5m
frecover(2105): did not find expected file marker
frecover(5409): unable to read volume header
frecover(5418): not an... (2 Replies)
Discussion started by: gummysweets
2 Replies
3. HP-UX
Hi All,
We have about 7 years worth of data which used the HP fbackup utility. Is there any utility to read these tapes on Solaris? The goal is to create new tapes using Legato.
Do we need to download them to a box first using frecover, then copy them from SUN using Legato?
Any help in... (0 Replies)
Discussion started by: tinakumar
0 Replies
4. HP-UX
Hi,
I have a tape fbackup done (fbackup -f /dev/rmt/0m -i / -I index.fullfbackup) and I need to restore 3 filesystems, I would like to know the correct command and options:
example:
I want to restore the filesystem /data1 under /data1
and /data2 under another filesystem /datatest
I tried... (4 Replies)
Discussion started by: touny
4 Replies
5. HP-UX
I had to do a recovery and restore from backup (using ignite & backups from fbackup job) on hpux 10.20.
Problem is, all users (except root) receive error 'unknown user' when logging in (during script that checks quotas).
They can still successfully log in to the system.
However, the files... (9 Replies)
Discussion started by: mrviking
9 Replies
6. Red Hat
Hello All,
The frecover command on HP UX gives information about the backed up file in the format-
Magic Field:
Machine Identification:
System Identification:HP-UX
Release Identification:B.11.11
Node Identification:
User Identification:
Record Size:
Time:
Media Use:0
Volume Number:1... (1 Reply)
Discussion started by: shamik
1 Replies
LEARN ABOUT DEBIAN
sg_reset
SG_RESET(8) SG3_UTILS SG_RESET(8)
NAME
sg_reset - sends SCSI device, target, bus or host reset; or checks reset state
SYNOPSIS
sg_reset [-b] [-d] [-h] [-t] [-V] DEVICE
DESCRIPTION
The sg_reset utility with no options (just a DEVICE) reports on the reset state (e.g. if a reset is underway) of DEVICE. When given a -d,
-t, -b or -h option it requests a device, target, bus or host reset respectively.
The ability to reset a SCSI target (often called a "hard reset" at the transport level) was added in linux kernel 2.6.27 . Low level driv-
ers that support target reset hopefully reset a logical unit only when given the device reset (i.e. -d) option. This should removed the
ambiguity of whether "device" meant LU or target that we have had in the past.
In the linux kernel 2.6 series this utility can be called on sd, sr (cd/dvd), st or sg device nodes; if the user has appropriate permis-
sions.
In the linux kernel 2.4 series support for this utility first appeared in lk 2.4.19 and could only be called on sg device nodes. Various
vendors made this capability available in their kernels prior to lk 2.4.19.
OPTIONS
-b attempt a SCSI bus reset. This would normally be tried if the device reset (i.e. option -d) was not successful.
-d attempt a SCSI device reset. If the device seems stuck, this is the first reset that should be tried. This assumes the linux scsi
mid level error handler is not already in the process of resetting DEVICE.
-h attempt a host adapter reset. This would normally be tried if both device reset (i.e. option -d) and bus reset (i.e. option -b) were
not successful.
-t attempt a SCSI target reset. This assumes the linux scsi mid level error handler is not already in the process of resetting the tar-
get that contains the given DEVICE.
-V prints the version string then exits.
NOTES
The error recovery code within the linux kernel when faced with a SCSI command timing out and no response from the device (LU), first tries
a device reset and if that is not successful tries a target reset. If that is not successful it tries a bus reset. If that is not success-
ful it tries a host reset. Users of this utility should check whether such a recovery is already underway before trying to reset with this
utility. The "device,target,bus,host" order is also recommended (i.e. first start with the smallest hammer). The above is a generalization
and exact details will vary depending on the transport and the low level driver concerned.
SAM-4 defines a hard reset, a logical unit reset and a I_T nexus reset. A hard reset is defined to be a power on condition, a microcode
change or a transport reset event. A LU reset and an I_T nexus reset can be requested via task management function (and support for LU
reset is mandatory). In Linux the SCSI subsystem leaves it up to the low level drivers as to whether a "device reset" is only for the
addressed LU or all the LUs in the device that contains the addressed LU (i.e. a target reset). The additional of the target reset (i.e.
option -t) should give more control in this area. The "bus reset" is a transport reset and may be a dummy operation, depending on the
transport. A "host reset" attempts to re-initialize the HBA that the request passes through en route to the DEVICE. Note that a "host
reset" and a "bus reset" may cause collateral damage.
This utility does not allow individual SCSI commands (or tasks as they are called in SAM-4) to be aborted. SAM-4 defines ABORT TASK and
ABORT TASK SET task management functions for that.
Prior to SAM-3 there was a TARGET RESET task management function. Several transports still support that function and many associated linux
low level drivers map the -t option to it.
AUTHORS
Written by Douglas Gilbert.
COPYRIGHT
Copyright (C) 1999-2009 Douglas Gilbert
This software is distributed under the GPL version 2. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PUR-
POSE.
sg3_utils-1.28 July 2009 SG_RESET(8)