I suspect it's a CIFS locking issue. So, is there a way to *force* the automatic nightly snapshot to rollover? If not, I guess I'll just
hand-job
this to do "manual automatic" snapshots at midnight and `snap rename` the busy ones. <sigh> What's the use of having the automated capability if it doesn't work when files are locked, he sarcastically muttered under his breath... ;)
No, it's probably because you have a CIFS share defined on the snapshot.
It's ain't being dumped, and never has been, so it's a CIFS share issue.
Exactly. Doing 'cifs shares' should show you the share defined on the snapshot. (For NFS folks, a CIFS 'share' corresponds to an NFS 'export'.) You can do a 'cifs shares -delete sharename' to remove the share.
(`cifs sessions *` works. Wo-hoo! But, which one is holding that particular snapshot busy?)
Snapshots can't be held from expiring by open files. It's the fact that a share is defined on the snapshot that is the problem here. (Another good question for the FAQ I guess.)
Mark Muhlestein -- mmm@netapp.com