Hi Fábio!
> I've just installed OmniOS on a Supermicro Motherboard with a DOM
> device for boot .
>
> It is working fine, no issues ...
>
> But, the 64GB DOM has just 9GB of space left
>
> Can I delete something ( temp files, compacted installed packages, etc
> ) to free some space ?
You
I recall an interesting post by Chris Siebenmann about dump/swap sizes
(surprise) on OmniOS, here it is (the only one comment at time was mine :-)
):
https://utcc.utoronto.ca/~cks/space/blog/solaris/OmniOSDiskSizing?showcomments#comments
Cheers, Davide
On Thu, Jan 26, 2017 at 12:22 PM, Fábio
sorry, I forgot to change address to all list before send ...
-- Forwarded message --
From: Fábio Rabelo
Date: 2017-01-26 9:21 GMT-02:00
Subject: Re: [OmniOS-discuss] Install on Supermicro DOM=low space left
To: "Volker A. Brandt"
Hi Fábio,
Am 26.01.17 um 12:22 schrieb Fábio Rabelo:
sorry, I forgot to change address to all list before send ...
-- Forwarded message --
From: Fábio Rabelo
Date: 2017-01-26 9:21 GMT-02:00
Subject: Re: [OmniOS-discuss] Install on Supermicro DOM=low
But dumps can also be saved as files on a normal dataset, right? provided
enough space is left for them.
Olaf
Il 26 gennaio 2017 12:38:27 CET, v...@bb-c.de ha scritto:
>> NAME USED AVAIL REFER MOUNTPOINT
>> rpool/dump 41.5G 9.15G 41.5G -
>> rpool/swap 4.13G 13.0G 276M -
>
On Thu, Jan 26, 2017 at 2:12 PM, Olaf Marzocchi wrote:
> But dumps can also be saved as files on a normal dataset, right? provided
> enough space is left for them.
>
No. The dump is a two-stage process.
When the system panics, it simply drops memory into the dump volume.
> NAME USED AVAIL REFER MOUNTPOINT
> rpool/dump 41.5G 9.15G 41.5G -
> rpool/swap 4.13G 13.0G 276M -
The "dump" volume is much too big. Do a
dumpadm -e
This will print the "estimated" dump size. Then add a bit, and
set the new dump volume size with:
zfs set volsize=
All supported releases (r151014, r151018, r151020) now have updated OpenSSL
from this morning's 1.0.2k update.
Please "pkg update" your supported OmniOS deployments. This is a non-reboot
update, but you may, depending, have to manually restart your openssl-using
services.
Dan
> On Jan 26, 2017, at 12:20 AM, Stephan Budach wrote:
>
> Hi Richard,
>
> gotcha… read on, below…
"thin provisioning" bit you. For "thick provisioning" you’ll have a
refreservation and/or reservation.
— richard
>
> Am 26.01.17 um 00:43 schrieb Richard Elling:
>>
Hi Richard,
gotcha… read on, below…
Am 26.01.17 um 00:43 schrieb Richard Elling:
more below…
On Jan 25, 2017, at 3:01 PM, Stephan Budach > wrote:
Ooops… should have waited with sending that message after I rebootet
the S11.1 host…
Am
Just for sanity… these are a couple of errors fmdump outputs using -eV
root@solaris11atest2:~# fmdump -eV
TIME CLASS
Jan 25 2017 10:10:45.011761190 ereport.io.pciex.rc.tmp
nvlist version: 0
class = ereport.io.pciex.rc.tmp
ena = 0xff37bc9a861
Hi to all
I've just installed OmniOS on a Supermicro Motherboard with a DOM
device for boot .
It is working fine, no issues ...
But, the 64GB DOM has just 9GB of space left
Can I delete something ( temp files, compacted installed packages, etc
) to free some space ?
I thing this 9GB free
12 matches
Mail list logo