`<html><head></head><body>But dumps can also be saved as files on a normal dataset, right? provided enough space is left for them.<br>
<br>
Olaf<br>
<br>
<br><br><div class="gmail_quote">Il 26 gennaio 2017 12:38:27 CET, vab@bb-c.de ha scritto:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"> NAME USED AVAIL REFER MOUNTPOINT<br /> rpool/dump 41.5G 9.15G 41.5G -<br /> rpool/swap 4.13G 13.0G 276M -<br /></blockquote><br />The "dump" volume is much too big. Do a<br /><br /> dumpadm -e<br /><br />This will print the "estimated" dump size. Then add a bit, and<br />set the new dump volume size with:<br /><br /> zfs set volsize=<new size> rpool/dump<br /><br />For example, on my OmniOS file server:<br /><br /># dumpadm -e<br />Estimated dump size: 4.63G<br /><br /># zfs set volsize=6G rpool/dump<br /><br /># zfs list rpool/dump<br />NAME USED AVAIL REFER MOUNTPOINT<br />rpool/dump 6.00G 24.1G 6.00G -<br /><br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"> I did not changed anything during instalation proccess, I've just<br /> accepted all defaults<br /></blockquote><br />Yes. The "traditional" installation usually sizes dump too big.<br />That is why I asked. :-)<br /><br /><br />Hope this helps -- Volker</pre></blockquote></div></body></html>`