We are using snv_111 and looking at that bug, it should've been fixed for this
version.
# cat /etc/release
OpenSolaris 2009.06 snv_111b X86
Copyright 2009 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 07 May 2009
On Apr 14, 2010, at 8:52 AM, Tim Foster wrote:
> On Wed, 2010-04-14 at 08:48 -0700, melbogia wrote:
>
>> It seems it was not able to take a recursive snapshot of
>> datap...@zfs-auto-snap:daily-2010-04-13-00:00 and dropped down to
>> maintenance. Would it be possible to find more information about why
>> it was unable to do that?
>
> Is this an old system? There was a ZFS bug
> http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6462803
>
> which we used to hit quite frequently.
>
> cheers,
> tim
>
>> I was not aware of 'svcadm mark..', which is nice.
>>
>>
>> On Apr 14, 2010, at 8:36 AM, Tim Foster wrote:
>>
>>> On Wed, 2010-04-14 at 08:28 -0700, melbogia wrote:
>>>> Hello,
>>>> Yesterday the zfs/auto-snapshot:daily service went into maintenance
>>>> mode and I am trying to figure out why. This is what I see but nothing
>>>> explains why it went into maintenance mode.
>>>
>>> There's a bunch of reasons why we can drop to maintenance. The service
>>> should have logged the reason to syslog (/var/adm/messages) though.
>>>
>>> Apart from during service start/stop, at the moment the auto-snapshot
>>> jobs run from a cron job as a non-root user, and as such, can't write to
>>> the SMF logs.
>>>
>>> It would be nice to be able to provide a message along with the call to
>>> 'svcadm mark maintenance <instance>' to explain why we're dropping the
>>> service to maintenance.
>>>
>>>> I tried disabling and enabling the service and it came back up. But why
>>>> did it went down?
>>>
>>> There should be info in syslog.
>>>
>>> cheers,
>>> tim
>>>
>>
>
>
_______________________________________________
opensolaris-help mailing list
[email protected]
