Snapshot restore operation fails to restore file system on raw LUN
Contributors
-
PDF of this doc site
-
Administration for Linux
-
Role-based access control in SnapDrive for UNIX
-
-
Installation and Administration for Solaris
-
Role-based access control in SnapDrive for UNIX
-
Creating and using Snapshot copies in SnapDrive for UNIX
-
-
Installation and Administration for IBM AIX
-
Role-based access control in SnapDrive for UNIX
-
-

Collection of separate PDF docs
Creating your file...
This may take a few minutes. Thanks for your patience.
Your file is ready
The Snapshot restore operation of the file system on raw LUN fails after performing a Snapshot connect operation on a non-originating host.
When the cloned LUN is connected to the same filespec in a Snapshot copy and then you try to execute the snapdrive snap restore command, the following error message appears.
"0001-034 Command error: mount failed: mount: <device name> is not a valid block device"
The command fails because the iSCSI daemon remaps the device entry for the restored LUN when you delete the cloned LUN.
Workaround
You can do any of the following:
-
Execute the
snapdrive snap restore
command again. -
Delete the connected LUN (if it is mounted on the same filespec as in Snapshot copy) before trying to restore a Snapshot copy of an original LUN.