SC 4.0 on linux mount operation failed

mpichlbauer — Thu, 05 Jun 2025 05:50:18 GMT

netapp01> Tue Nov 5 12:11:31 CET [netapp01: app.log.info:info]: emanasc01 [10.200.200.61:9090]: SNAPCREATOR Snap Creator Framework 4.0p1: (0) Backup Started: INFO: Snap Creator Framework 4.0p1 Backup for suite6nadb1-dirty ACTION: cloneVol POLICY: hourly Plugin: No plugin configuration Volumes: suite6db, Started

Tue Nov 5 12:11:35 CET [netapp01: wafl.vvol.offline:info]: Volume 'cl_suite6nadb1_dirty_suite6db_20131018124146' has been set temporarily offline

Tue Nov 5 12:11:37 CET [netapp01: wafl.vvol.destroyed:info]: Volume cl_suite6nadb1_dirty_suite6db_20131018124146 destroyed.

Tue Nov 5 12:11:38 CET [netapp01: app.log.info:info]: emanasc01 [10.200.200.61:9090]: SNAPCREATOR Snap Creator Framework 4.0p1: (0) Backup Completed: INFO: Snap Creator Framework 4.0p1 Backup for suite6nadb1-dirty ACTION: cloneVol POLICY: hourly Plugin: No plugin configuration Volumes: suite6db, finished

Tue Nov 5 12:11:42 CET [netapp01: wafl.volume.clone.created:info]: Volume clone cl_suite6nadb1_dirty_suite6db_20131105121131 of volume suite6db was created successfully.

Tue Nov 5 12:11:42 CET [netapp01: lun.newLocation.offline:warning]: LUN /vol/cl_suite6nadb1_dirty_suite6db_20131105121131/db/suite6db.lun has been taken offline to prevent map conflicts after a copy or move operation.

Why the lun is being taken offline? how can I manage to get that "mountable"?

Snap Creator output:

########## Detecting Data ONTAP mode for netapp01 ##########

[2013-11-05 12:11:31,665] INFO: STORAGE-03031: System version details of [netapp01].

[2013-11-05 12:11:31,665] INFO: STORAGE-03032: System version details of [netapp01] finished successfully.

########## Agent validation ##########

[2013-11-05 12:11:31,666] INFO: Application commands and plug-in not defined. Skipping Agent validation task

########## Plugin validation ##########

[2013-11-05 12:11:31,667] INFO: Application not defined. Skipping Plugin validation task

[2013-11-05 12:11:31,668] INFO: Removing log suite6nadb1_dirty.debug.20131017111403.log

[2013-11-05 12:11:31,669] INFO: Removing log suite6nadb1_dirty.out.20131017111403.log

########## PRE APPLICATION QUIESCE COMMANDS ##########

[2013-11-05 12:11:31,670] INFO: Pre application quiesce commands are not defined

########## PRE APPLICATION QUIESCE COMMANDS FINISHED SUCCESSFULLY ##########

[2013-11-05 12:11:31,670] INFO: Application not defined. Skipping Discovery task

[2013-11-05 12:11:31,670] INFO: Application not defined. Skipping validate volume task

########## Application Quiesce ##########

########## Application not defined. Skipping Quiesce task ##########

########## APPLICATION QUIESCE COMMANDS ##########

[2013-11-05 12:11:31,679] INFO: Application quiesce commands are not defined

########## APPLICATION QUIESCE COMMANDS FINISHED SUCCESSFULLY ##########

########## POST APPLICATION QUIESCE COMMANDS ##########

[2013-11-05 12:11:31,683] INFO: Post application quiesce commands are not defined

########## POST APPLICATION QUIESCE COMMANDS FINISHED SUCCESSFULLY ##########

########## PRE NTAP COMMANDS ##########

[2013-11-05 12:11:31,684] INFO: Pre ntap commands are not defined

########## PRE NTAP COMMANDS FINISHED SUCCESSFULLY ##########

########## Generating Info ASUP on netapp01 ##########

[2013-11-05 12:11:31,700] INFO: STORAGE-01001: Creating autosupport message with event id [0], category [Backup Started], description [INFO: Snap Creator Framework 4.0p1 Backup for suite6nadb1-dirty ACTION: cloneVol POLICY: hourly Plugin: No plugin configuration Volumes: suite6db, Started], level [INFO], hostname [emanasc01 [10.200.200.61:9090]].

[2013-11-05 12:11:31,700] INFO: STORAGE-01002: Creating autosupport message with event id [0], category [Backup Started], description [INFO: Snap Creator Framework 4.0p1 Backup for suite6nadb1-dirty ACTION: cloneVol POLICY: hourly Plugin: No plugin configuration Volumes: suite6db, Started], level [INFO], hostname [emanasc01 [10.200.200.61:9090]] finished successfully.

[2013-11-05 12:11:31,700] INFO: ASUP finished successfully on netapp01

########## PRE CLONE DELETE COMMANDS ##########

[2013-11-05 12:11:31,701] INFO: Pre clone delete commands are not defined

########## PRE CLONE DELETE COMMANDS FINISHED SUCCESSFULLY ##########

########## Executing vol clone Delete ##########

[2013-11-05 12:11:31,920] INFO: STORAGE-02130: Listing cloned volumes based on volume [null].

[2013-11-05 12:11:31,920] INFO: STORAGE-02131: Listing cloned volumes based on volume [null] finished successfully.

[2013-11-05 12:11:37,320] INFO: STORAGE-02140: Deleting volume [cl_suite6nadb1_dirty_suite6db_20131018124146].

[2013-11-05 12:11:37,320] INFO: STORAGE-02141: Deleting volume [cl_suite6nadb1_dirty_suite6db_20131018124146] finished successfully.

########## Running Snapshot copy Rename on Primary devices ##########

[2013-11-05 12:11:37,322] INFO: Skipping Snapshot copy rename

########## File system plug-in not defined. Skipping file system quiesce ##########

########## SNAPSHOT CREATE COMMANDS ##########

########## Snapshot copy create commands finished successfully ##########

[2013-11-05 12:11:37,325] INFO: Skipping consistency group Snapshot copy

########## Taking Snapshot copy on Primary netapp01:suite6db ##########

[2013-11-05 12:11:38,414] INFO: STORAGE-02007: Creating Snapshot copy [suite6nadb1-dirty-hourly_20131105121131] on volume [suite6db].

[2013-11-05 12:11:38,414] INFO: STORAGE-02008: Snapshot copy [suite6nadb1-dirty-hourly_20131105121131] on volume [suite6db] created successfully.

########## Snapshot copy create of suite6nadb1-dirty-hourly_20131105121131 on netapp01:suite6db Completed Successfully ##########

########## File system plug-in not defined. Skipping file system unquiesce ##########

########## PRE APPLICATION UNQUIESCE COMMANDS ##########

[2013-11-05 12:11:38,416] INFO: Pre application unquiesce commands are not defined

########## PRE APPLICATION UNQUIESCE COMMANDS FINISHED SUCCESSFULLY ##########

########## Application not defined. Skipping Unquiesce task ##########

########## APPLICATION UNQUIESCE COMMANDS ##########

[2013-11-05 12:11:38,417] INFO: Application unquiesce commands are not defined

########## APPLICATION UNQUIESCE COMMANDS FINISHED SUCCESSFULLY ##########

########## POST APPLICATION UNQUIESCE COMMANDS ##########

[2013-11-05 12:11:38,420] INFO: Post application unquiesce commands are not defined

########## POST APPLICATION UNQUIESCE COMMANDS FINISHED SUCCESSFULLY ##########

########## Application Pre Clone ##########

########## Application not defined. Skipping PreClone task ##########

########## UMOUNT COMMANDS ##########

[2013-11-05 12:11:38,421] INFO: Umount commands are not defined

########## PRE CLONE CREATE COMMANDS ##########

[2013-11-05 12:11:38,422] INFO: Pre clone create commands are not defined

########## PRE CLONE CREATE COMMANDS FINISHED SUCCESSFULLY ##########

########## Generating Info ASUP on netapp01 ##########

[2013-11-05 12:11:38,432] INFO: STORAGE-01001: Creating autosupport message with event id [0], category [Backup Completed], description [INFO: Snap Creator Framework 4.0p1 Backup for suite6nadb1-dirty ACTION: cloneVol POLICY: hourly Plugin: No plugin configuration Volumes: suite6db, finished], level [INFO], hostname [emanasc01 [10.200.200.61:9090]].

[2013-11-05 12:11:38,432] INFO: STORAGE-01002: Creating autosupport message with event id [0], category [Backup Completed], description [INFO: Snap Creator Framework 4.0p1 Backup for suite6nadb1-dirty ACTION: cloneVol POLICY: hourly Plugin: No plugin configuration Volumes: suite6db, finished], level [INFO], hostname [emanasc01 [10.200.200.61:9090]] finished successfully.

[2013-11-05 12:11:38,432] INFO: ASUP finished successfully on netapp01

[2013-11-05 12:11:38,433] WARN: Configuration not enabled for snapvault!

########## Running Snapshot copy Rename on Secondary devices ##########

[2013-11-05 12:11:38,435] WARN: Configuration not enabled for snapvault!

########## POST DATA TRANSFER COMMANDS ##########

[2013-11-05 12:11:38,436] INFO: No commands defined

########## POST DATA TRANSFER COMMANDS FINISHED SUCCESSFULLY ##########

########## Executing Vol Clone ##########

[2013-11-05 12:11:38,437] INFO: Creating Volume Clone from Snapshot copy suite6nadb1-dirty-hourly_20131105121131 of netapp01:suite6db

[2013-11-05 12:11:42,726] INFO: STORAGE-02036: Creating clone [cl_suite6nadb1_dirty_suite6db_20131105121131] of volume [suite6db] based on Snapshot copy [suite6nadb1-dirty-hourly_20131105121131].

[2013-11-05 12:11:42,729] INFO: STORAGE-02037: Creating clone [cl_suite6nadb1_dirty_suite6db_20131105121131] of volume [suite6db] based on Snapshot copy [suite6nadb1-dirty-hourly_20131105121131] finished successfully.

[2013-11-05 12:11:42,730] INFO: Successfully created volume clone from Snapshot copy suite6db of netapp01:suite6db

[2013-11-05 12:11:42,772] INFO: STORAGE-02050: Listing luns.

[2013-11-05 12:11:42,772] INFO: STORAGE-02051: Listing luns finished successfully.

########## POST DATA TRANSFER COMMANDS ##########

[2013-11-05 12:11:42,773] INFO: No commands defined

########## POST DATA TRANSFER COMMANDS FINISHED SUCCESSFULLY ##########

########## Running Snapshot copy Delete on Primary ##########

[2013-11-05 12:11:42,839] INFO: STORAGE-02090: Listing Snapshot copies on volume [suite6db].

[2013-11-05 12:11:42,839] INFO: STORAGE-02091: Listing Snapshot copies on volume [suite6db] finished successfully.

########## POST CLONE CREATE COMMANDS ##########

[2013-11-05 12:11:42,840] INFO: Post clone create commands are not defined

########## POST CLONE CREATE COMMANDS FINISHED SUCCESSFULLY ##########

########## MOUNT COMMANDS ##########

[2013-11-05 12:11:42,841] INFO: Mount commands are not defined

########## Application Post Clone ##########

########## Application not defined. Skipping PostClone task ##########

########## POST NTAP COMMANDS ##########

[2013-11-05 12:11:42,843] INFO: No commands defined

########## NTAP COMMANDS FINISHED SUCCESSFULLY ##########

########## ARCHIVE COMMANDS ##########

[2013-11-05 12:11:42,844] INFO: Archive commands are not defined

########## Snap Creator Framework 4.0p1 finished successfully ##########

[2013-11-05 12:11:42,868] INFO: INFO: Snap Creator finished successfully ( Action: cloneVol

Thanks in advance!

best regards

Manfred

Re: SC 4.0 on linux mount operation failed

clilescapario — Wed, 06 Nov 2013 16:48:42 GMT

Hello Manfred,

I believe your existing flexclone is getting destroyed because SC will only keep a limited number of clones around.

#     If true will reserve space for cloned luns if false will not                                                     
# NTAP_NUM_VOL_CLONES - (optional) - Number                                                                            
#     Setting which configures how many volume clones Snap Creator will keep

As for getting the luns mapped, please check that you have the option in your configuration set to tell SC where to map the clone luns to. I use the following in my clone configurations to map all luns that are contained in the newly created flexclone to an igroup.

# NTAP_CLONE_IGROUP_MAP - (optional) - Text                                                                       
#     List of filer(s), source volume(s), and the Igroups used to map cloned volumes and luns            
#     i. e.: controller1:src_volume1/igroup1;controller2:src_volume2/igroup2
NTAP_CLONE_IGROUP_MAP=filer1:volume1/igroup1

Clone and mount are pretty similar, I think that mount uses and existing snapshot while clone will take a new one.

Thanks,

Chris

Re: SC 4.0 on linux mount operation failed

sivar — Thu, 07 Nov 2013 02:19:16 GMT

http://support.netapp.com/NOW/download/software/snapcreator_framework/4.0P1D2/

Please try with the above version. There are fixes for luns under qtree.

Re: SC 4.0 on linux mount operation failed

sivar — Tue, 12 Nov 2013 14:10:10 GMT

Hello Manfred,
Please update this thread if you still need help.

Thanks,
Siva Ramanathan

Re: SC 4.0 on linux mount operation failed

mpichlbauer — Tue, 12 Nov 2013 14:13:00 GMT

HI Chris,

thank you for your answer.

we have already changed from lun clones to volume clone due to the reason that only one lun clone can be created with SC.

best regards

Manfred

Re: SC 4.0 on linux mount operation failed

mpichlbauer — Tue, 12 Nov 2013 14:14:04 GMT

Hi Siva,

we don't use luns in qtrees, are there also other mount issues fixed in the new version?

thanks

Manfred

Re: SC 4.0 on linux mount operation failed

sivar — Tue, 12 Nov 2013 14:20:03 GMT

Your syntax below shows there is a qtree called db and the lun is inside the qtree.

/vol/cl_suite6nadb1_dirty_suite6db_20131105121131/db/suite6db.lun

/vol/volumename/qtreename/lun

without qtree,

this would look like

/vol/cl_suite6nadb1_dirty_suite6db_20131105121131/suite6db.lun

topic Re: SC 4.0 on linux mount operation failed in Data Protection

SC 4.0 on linux mount operation failed

Re: SC 4.0 on linux mount operation failed

Re: SC 4.0 on linux mount operation failed

Re: SC 4.0 on linux mount operation failed

Re: SC 4.0 on linux mount operation failed

Re: SC 4.0 on linux mount operation failed

Re: SC 4.0 on linux mount operation failed