Core dump does not go into aggr snap reserve.  During panic, core is dumped into a reserved area (the space chopped off by rightsizing) on one or more non-broken disks (outside of WAFL, since WAFL code runs in memory, which we might no longer trust depending on what went wrong and we're dumping it).  During reboot, savecore (see the man pages and System Admin Guide) moves the core from reserved area to /etc/crash, where it can be picked up by the user or other process.
 
I could be wrong about which disks it uses, but I'm sure it doesn't use aggr snap reserve.
 
Peter

From: Michael Schipp [mailto:mschipp@asi.com.au]
Sent: Monday, December 18, 2006 2:54 PM
To: toasters@mathworks.com
Subject: Aggregrate snap reserve (again)

Hi all,

      We have had a lot of talk since DOT 7 of this but just to clear it up some (I hope).

 

 

aggregate snapshots are required if you use (default 5%);

·        RAID SyncMirror and/or MetroCluster configurations.

·        Aggr copy command

·        Core dump

 

IS the core dump in on aggr0 snap space only?

 

So if a Filer/FAS has two aggregates and not using or needing SyncMirror and the aggrcopy command is it safe to turn off the aggregate snap reserve for aggr1 (still leaving snap reserve on for aggr0 for core dumps)?

 

NetApp – are aggregates snap reserve used for any other purpose?

 

Thanks

Michael