Note that snap status is an advanced command so its output shouldn't necessarily cause you concerns...<br>There is some metadata activity that occurs after a snapshot is created - the filer can reboot/crash in the middle with no harm since like anything on the filer this is a logged and consistent operation.
<br><br>Eyal<br><a href="http://filers.blogspot.com">http://filers.blogspot.com</a><br><br><br><br><div><span class="gmail_quote">On 9/7/06, <b class="gmail_sendername">ec0li</b> &lt;<a href="mailto:ecoli82@msn.com">ecoli82@msn.com
</a>&gt; wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>Hello,<br><br>When I check snap status, I see next to recent snapshots : (xxxx/xxxx
<br>remaining).<br>Also, It seems that this is in fact the wafl scan process &quot;snap create<br>summary update&quot;<br><br>Does anyone knows what is this process, its purpose, what happens if the<br>system reboots during this,...
<br><br>I'm asking this because on one system with lots of snapshots(snapvault) this<br>process seems to never finish. In fact, each time a new snap is transfered<br>the counter restarts from the beginning but has not enough time to finish
<br>until a new snapshot is created.<br>Consequence : in snap status I see more and more snapshots with (xxx/xxx<br>remaingint) on the right.<br><br>Thanks in advance for your answers!<br>--<br>View this message in context: 
<a href="http://www.nabble.com/Snap-status-and-wafl-scan-tf2232129.html#a6187160">http://www.nabble.com/Snap-status-and-wafl-scan-tf2232129.html#a6187160</a><br>Sent from the Network Appliance - Toasters forum at <a href="http://Nabble.com">
Nabble.com</a>.<br><br></blockquote></div><br><br clear="all"><br>-- <br>Yours,<br>Eyal.