Arnie Thompson arnie@netapp.com writes:
When you delete files, the space formerly accounted for in the active file system now gets accounted for in the .snapshot area. Snapshot space consumed grows as you delete or modify files, and the more you change the larger the snapshot area becomes; think of snapshots as measuring the "delta" in a file system.
It would really be great if there was a snapshot deletion daemon that could delete the oldest standard (hourly, nightly, and weekly snapshots only) snapshot(s) when the snapshot usage goes above a certain number.
So, "snap" could do a "snap highwatermark" command or something like that in a similar manner to the "snap reserve" command.
- Dan
It would really be great if there was a snapshot deletion daemon that could delete the oldest standard (hourly, nightly, and weekly snapshots only) snapshot(s) when the snapshot usage goes above a certain number.
So, "snap" could do a "snap highwatermark" command or something like that in a similar manner to the "snap reserve" command.
Sounds like a trivial job for a little cron job with a couple of rsh commands. I'd probably trap it via snmp and then issue an rsh snap delete to remove the oldest snapshot. I suppose it could be useful if the Netapp had its own cron mechanism, although I'd rather see the NetApp kernel stay small and simple and let the NetApp do what it is good at.
-Rasmus
-
Daniel Quinlan -
rasmus＠lerdorf.on.ca