good day all ...
i've got a snapshot i cannot delete because its 'busy':
poplar> snap list Volume vol0 working.....................................................
%/used %/total date name ---------- ---------- ------------ -------- 1% ( 1%) 1% ( 1%) Jan 11 12:01 hourly.0 1% ( 1%) 1% ( 1%) Jan 11 08:01 hourly.1 1% ( 1%) 1% ( 1%) Jan 11 00:01 nightly.0 1% ( 1%) 1% ( 1%) Jan 10 20:01 hourly.2 2% ( 1%) 1% ( 1%) Jan 10 16:01 hourly.3 2% ( 1%) 1% ( 1%) Jan 10 12:01 hourly.4 2% ( 1%) 1% ( 1%) Jan 10 08:02 hourly.5 4% ( 2%) 3% ( 2%) Jan 10 00:02 nightly.1 19% (16%) 15% (13%) Dec 24 21:42 snapshot_for_backup.68 (busy)
when i try do delete the snapshot i get:
poplar> snap delete snapshot_for_backup.68 Snapshot in use by dump or a CIFS share.
even though cifs and ndmpd are not running. how do i delete this snapshot while keeping the filer online? this is an F520/OT5.3.4R2 system. thanks!
when i try do delete the snapshot i get:
poplar> snap delete snapshot_for_backup.68 Snapshot in use by dump or a CIFS share.
even though cifs and ndmpd are not running. how do i delete this snapshot while keeping the filer online? this is an F520/OT5.3.4R2 system. thanks!
Unless the dump terminate command was finally implemented (asked for since about v 2.1), you can't. I'm assuming dump is the problem here and not CIFS, since CIFS terminate should normally take care of any CIFS problems. Your best bet is to just do a reboot, which will only interrupt service for a few minutes.
Bruce
Bruce Sterling Woodcock wrote:
Your best bet is to just do a reboot, which will only interrupt service for a few minutes.
I see people say that a lot: "Just reboot, service will be interrupted for only a moment." or "No one will notice."
That's true for NFS, but it royally pisses off my CIFS users whenever I do that, as they lose work, so I never "just reboot" to fix anything. Rebooting is the LAST resort to fixing a problem. I really don't see how you folks can get away with it without your CIFS users lynching you ...
-ste
Bruce Sterling Woodcock wrote:
Your best bet is to just do a reboot, which will only interrupt service for a few minutes.
I see people say that a lot: "Just reboot, service will be interrupted for only a moment." or "No one will notice."
That's true for NFS, but it royally pisses off my CIFS users whenever I do that, as they lose work, so I never "just reboot" to fix anything. Rebooting is the LAST resort to fixing a problem. I really don't see how you folks can get away with it without your CIFS users lynching you ...
Yes, but he said CIFS was already disabled.
Bruce
PS - Considering how often NT servers have to be rebooted to fix problems, I would think CIFS users would be used to it anyway... :)