Unable to stop snapshot

[joe-farka]

Hi,


After an rsync (from another machine to the Open-e NAS) freeze, I am suddenly not able to stop a snapshot neither through web interface (the system refresh the sub-window and... nothing) nor the command line with the appropriate ssh command (which just return "Operation failed" for stop command, "active" for status command and "Task already started" for start command).

In addition (I guess it is the cause of the rsync freeze), in Configuration > NAS resources > Shares > snap_users (which the share that I have created to access the snapshot through the network), I have the "Warning..." message which tells me that the path to this share does not exist as an inactive snapshot.

I would appreciate any help.

Thanks,
joe

[To-M]

If this is a new setup then try to make sure that the Snapshot is not being used by any other functions. Check the Snapshot to be sure that it is only for the Data Replication for the NAS volume that you are using. Update to version 5087 there was some improvements with the Data Replication.

How many files are you replicating and what size variables are they so lets say 100 or 1 Million files (small or large or both).

[joe-farka]

Thanks Todd,

this is not a new setup and snapshots started and stopped well until today.
How to check (exhaustively) if the snapshot is used by other functions?
I am replicating more than 100K files and size of files varies from 1KB to more than 1GB.
Do I have to restart after update? I guess yes. Because I have about twenty VMs in production.
Should I try "Remove all snapshots" in Expert Tools? What are the consequences?

Thanks a lot,
joe

[To-M]

You can check if Snapshots are used or assigned to the volumes from the Volume manager and there you should see a check mark if assigned to the volumes.
Is the Snapshot large enough to the volume at least 12% of the total volume size?

You will have to restart after update. If the update does not fix the Snapshot still unable to remove then yes use the Extended tools but there will be a restart.

[joe-farka]

Hi Todd,

sorry for the delay, I had a lot of work.
I have rebooted the NAS this morning. It takes me 1 hour because my external LDAP (as declared in the NAS) was down (because it is a VM). And so the NAS was a little bit lost without connection to its LDAP. I had to turn into internal LDAP, reboot it again because NFS was crashed. Once up and NFS working, start my VMs (then the ldap server) and turn into external LDAP again. Perhaps there are some tickets on it (??).

Anyway, after that pain, I was able to turn off my snapshot (without update).

Thank you very much Todd for your help.

joe
ps: I do not know if there is a way to turn this thread to solved.

[To-M]

Hey Joe - Thanks for the update, I checked for any tickets and found none but we could post on our knowledge base for an article.