[OpenIndiana-discuss] Disk Free Question

[James Carlson]

On 07/07/14 15:52, DormitionSkete at hotmail.com wrote:
> Then I thought, well, maybe something in the zones are causing this, so I booted them back up and ran dmesg again.
> 
> "# dmesg” — with the non-global zones running — shows this:

The first thing that really stands out to me is this:

> Jul  7 12:56:29 baptist.ds svc.startd[10]: [ID 122153 daemon.warning] svc:/network/location:default: Method or service exit timed out.  Killing contract 61.
> Jul  7 12:56:29 baptist.ds svc.startd[10]: [ID 636263 daemon.warning] svc:/network/location:default: Method "/lib/svc/method/net-loc start" failed due to signal KILL.

That looks like a waste of time.  If this isn't a portable system (i.e.,
a laptop), then I'd disable that service.  Or at least look into why
it's failing miserably and slowing down the boot process.

> Jul  7 12:58:39 baptist.ds upsd[679]: [ID 702911 daemon.error] not listening on 192.168.0.5 port 3493
> Jul  7 12:58:39 baptist.ds upsd[679]: [ID 702911 daemon.error] no listening interface available

Also, it looks like your UPS daemon might have configuration problems.

> Jul  7 13:26:52 baptist.ds time-sliderd: [ID 702911 daemon.notice] No more hourly snapshots left
> Jul  7 13:26:52 baptist.ds time-sliderd: [ID 702911 daemon.warning] rpool exceeded 80% capacity. Hourly and daily automatic snapshots were destroyed
> Jul  7 13:26:52 baptist.ds time-sliderd: [ID 702911 daemon.notice] 239 automatic snapshots were destroyed

Yow.  That would certainly take some time.

For what it's worth, I don't run time slider.  I do my own snapshots
using my own scripts.  I ran into problems with the early
implementations of time slider and just gave up on it.

I can't speak to its current incarnation, because I'm uninterested in
using it.  Your mileage may vary.

-- 
James Carlson         42.703N 71.076W         <carlsonj at workingcode.com>