revert_to does require all volume and aggr snapshots made on the new release to be deleted before a reversion can take place. I can see where this would be somewhat of a discomfort when using things such as snapvault ;)
You should be able to use the revert_to command in order to get to 7.2.3, but should check w/ support first.
Christopher Mende
Sr Solutions Architect
Peak UpTime
+1 913 523 4263
-----Original Message-----
From: Conner, Neil <neil@mbari.org>
Sent: Thursday, June 12, 2008 12:31
To: Pascal Dukers <pascal.dukers@asml.com>; Toasters <toasters@mathworks.com>
Subject: Re: Another 7.2.5 quota bug
I downgraded to 7.2.4 last night and that solved the problem.
It was a real show stopper for me because the only way to quiet the errors
was to turn quotas off.
On 6/11/08 11:20 PM, "Pascal Dukers" <pascal.dukers@asml.com> wrote:
>
>
>
> Conner, Neil wrote:
>>
>> Since upgrading from 7.2.3 to 7.2.5 on a pair of clustered 3020s, the
>> consoles has been overrun with the following errors:
>>
>> [toaster: quota.softlimit.normal:notice]: Soft file limit returned to
>> normal for tree 92 on volume vol0
>>
>> The syslog buffers are getting overrun, messages are getting dropped, and
>> the syslog is ready to fill the root volume.
>>
>> We donšt set file quotas at all. Tried stopping and restarting quotas and
>> disabling SNMP all to no avail. Support has no fix for this so they
>> recommended I downrev to 7.2.4. I canšt revert back to 7.2.3 because
>> something changed in WAFL.
>>
>> Anyone else seen this?
>>
>>
>
>
> I have hit exactly the same bug on multiple filers and also don't use (soft)
> file limits. Hopefully support comes with a workaround in 7.2.5 and/or a
> patch soon.