Overview: The Next Generation Mass Storage Stack (September 2009)

–L Creates legacy DSFs and enables the support of legacy DSFs. When used with the–v option, insf
–L reports whether the legacy mode is enabled or disabled. For example:
# insf –Lv
insf: Legacy mode enabled
lssf(1M)
The lssf command displays information about a DSF. For persistent DSFs, the output shows the LUN hardware
path. For example:
# lssf /dev/dsk/c2t0d0
sdisk card instance 2 SCSI target 0 SCSI LUN 0 section 0 at address 0/1/1/0.0.0
/dev/dsk/c2t0d0
# lssf /dev/disk/disk47
esdisk section 0 at address 64000/0xfa00/0x0 /dev/disk/disk47
The lssf command also supports two new options:
–s Displays stale DSFs (DSFs for which the hardware is not accessible). The output can contain both
legacy and persistent DSFs. For example:
# lssf –s
Stale Block Device Files
------------------------
/dev/dsk/c4t0d0
/dev/dsk/c4t1d0
/dev/dsk/c4t3d0
/dev/disk/disk18
/dev/disk/disk19
Stale Character Device Files
----------------------------
/dev/rdsk/c4t0d0
/dev/rdsk/c4t1d0
/dev/rdsk/c4t3d0
/dev/rdisk/disk18
/dev/rdisk/disk19
–c Performs critical resource analysis on a specified DSF. You can use this option during migration to
confirm that an application is not using legacy DSFs.
mksf(1M)
The mksf command creates a single DSF. In HP-UX 11i v3, it enables the –H option to use lunpath hardware
paths. The mksf command supports one new option:
–P Creates a pass-through persistent DSF for the esdisk, estape, and eschgr drivers.
rmsf(1M)
The rmsf command removes DSFs and device definitions from the system. It supports the following new options:
–u Unbinds a driver from a given hardware path when used with the –H option, as described in Force-
Binding a Driver.
20