Owner's manual

The /E indicates that what follows is an Expand filename. The /G indicates that what follows is a
Guardian filename. Note that the $ (dollar sign) is omitted from the volume name. When the system
encounters one of these OSS pathnames, it converts the name to a Guardian filename using the
following conventions:
• /E/nodename is converted to \nodename.
• The /G/ is replaced by a $ (dollar sign).
• The / (slash) preceding fileid is interpreted as a . (period).
• Alphabetic characters (except /G or /E) are converted to lowercase.
If the following characters (common in OSS filenames) are included in the pathname, they are
dropped in the translation:
period.
comma,
hyphen-
underscore_
Following are four examples of conversions from OSS pathnames to Guardian filenames:
Guardian FilenameOSS Pathname
$data.mysubvol.file/G/data/mysubvol/file
\node1.$data.mysubvol.file/E/node1/G/data/mysubvol/file
$datavol.src11v34.properti/G/data.volume/src.11.v3.4.8
/properties.c
$disk/G/disk
$ztnt.#pty7/G/ztnt/#pty7
The following are examples of invalid translation attempts:
Will not translate to a Guardian name because it includes
too many levels.
/G/data/a/b/c
Will not translate to a Guardian name because it contains
an invalid character (a colon).
/G/oss/src:v3.4/logger.c
If you specify an invalid filename or pathname, the related operation terminates with the error
ENOENT. When you attempt to create a file with an invalid name, the operation terminates with
the error EINVAL.
Guardian Filename to OSS Pathname Translation
Following are examples of how Guardian filenames translate into OSS pathnames.
OSS PathnameGuardian Filename
/G/vol$VOL
/G/vol$vol
/G/vol/subvol$vol.subvol
/G/p/#1234$P.#1234
Guardian Filename to OSS Pathname Translation 71