Hello,
I did some checking and found another Symantec reference that suggests the filesystem byte-order conversion using
fscdsconv needs to be done on the Solaris side first before it is exported to the Linux system:
REF: https://support.symantec.com/en_US/article.TECH140562.html
The manpage for fscdsconv it its "-e" option you are using also states the same thing where the conversion
should be done first on the source side, exported, and then imported on the Linux side:
https://sort.symantec.com/public/documents/sf/5.0/solaris/manpages/vxfs/fscdsconv_1m.html
"
OPTIONS
-e
Exports the file system for use on the specified target. The fscdsconv command reports detailed information regarding the migration target, and waits for user confirmation before proceeding with the migration. If the target must be changed or further refined, the user can abort the migration at this stage and restart with a new target specification.
The fscdsconv command validates the file system to determine if there are any files that violate the known maximum limits of file size, UID, or GID on the target system, reports any such violations, and waits for user confirmation before proceeding. If any violations are reported, Symantec recommends that you abort the migration, rectify the violations, then restart the migration.
If the file system metadata must be byteswapped for use on the specified target, fscdsconv waits for user confirmation before proceeding with the migration.
After the export is complete and reported to be successful, the file system is ready for use on the target. If byteswapping was done as part of the export, the file system will no longer be accessible on the source machine."
Alternatively, the manpage does show the "-i" option which may be what you want to use if doing the conversion on
the Linux side:
"-i
Imports the file system for use on the current system. The fscdsconv command validates the file system to determine if there are any files that violate the known maximum limits of the file size, UID, or GID on the system, reports any such violations, and waits for user confirmation before proceeding. If any violations are reported, you may either abort the import, mount the file system on the source system, rectify the violations, then restart the import on the system, or proceed with the migration and rectify the violations after the migration completes.
If the file system metadata needs to be byteswapped for use on the system, the fscdsconv command waits for user confirmation before proceeding with the migration."
Caution: One should always have a backup of the original file system before performing conversion operations.
NOTE: One or more of the links above will take you outside the Hewlett-Packard Web site, HP does not control and is not responsible for information outside of the HP Web site.