lsd(1M)                          DG/UX R4.11                         lsd(1M)


NAME
       lsd - load or transfer a system dump

SYNOPSIS
       lsd [ -s ] [ -d dirname ] tapedev

       lsd -t vddev tapedev

DESCRIPTION
       The lsd(1M) command loads or transfers a dump image that was produced
       after a system halt or hang. The command has two versions, listed
       above and illustrated below. The first version loads a system dump
       image from tape to a disk directory. The second version transfers a
       system dump image from a virtual disk to tape. Both versions support
       multi-volume tape sets.  See CAUTIONS below for restrictions that
       apply when loading the dump image into a disk.

       The options and arguments are:

       tapedev       Enter the pathname of the tape device containing the
                      tape(s) to be loaded (version 1), or to transfer the
                      dump image to (version 2).  Both versions require this
                      argument.

                      For version 1 (tape to disk), enter the device node
                      that specifies no-rewind; for version 2 (disk to
                      tape), specify rewind.  (See the examples, below.)

       -s             Do not complain if the dump includes no kernel
                      executable image.

       -d [dirname]  Load the dump image from the tape(s) in tapedev into
                      the directory dirname, or into the current directory
                      if no dirname is specified.  If dirname does not
                      exist, lsd(1M) creates it.

       -t vddev      Transfer the dump image from vddev to the tape(s) in
                      tapedev.  For vddev, enter the pathname of the
                      virtual disk containing the system dump (for example,
                      /dev/rdsk/sysdump).

       The default dump device is initially set to the value of the kernel
       tunable parameter named DUMP, which can be explicitly specified in
       the DG/UX system configuration file if its normal value is
       unsatisfactory.  Once the kernel is up and running, you can also use
       the dgsysctl(1M) command to display or change the default dump
       device or other halt dump parameters.

       System dump images are important for reporting system problems to
       Data General. See the Release Notice for instructions.

DIAGNOSTICS
       Diagnostic and error messages are routed to standard output and
       standard error, respectively.

       The following exit values are returned:

        0  Successful completion.

       >0  An error occurred.

EXAMPLE
       Load a dump image into the current directory, from a dump tape in the
       specified tape drive (note the no-rewind option):

       lsd /dev/rmt/0n

       Transfer a dump image from the specified virtual disk to a tape in
       the specified tape drive (note the rewind option):

       lsd -t /dev/rdsk/sysdump /dev/rmt/0

SEE ALSO
       crash(1M), dgsysctl(1M)

CAUTIONS
       You can load the dump image into a virtual disk only if it resides
       entirely on a local SCSI disk.  You cannot load into a virtual disk
       that comprises multiple partitions spanning multiple physical disks
       or to any virtual disk residing on an SMD or ESDI physical disk.  The
       load process will write over any data, such as a file system, that
       resides on the virtual disk at the time of the load.  Therefore, you
       should not create a file system on the disk and attempt to use it for
       any purpose other than to contain the load.  For the same reason,
       there should be no file system entry in /etc/fstab that uses the
       virtual disk.





Licensed material--property of copyright holder(s)