[OpenIndiana-discuss] Unusual prb: crash during update stole my disk space

[Andreas Wacknitz]

Am 04.10.25 um 21:50 schrieb dan via openindiana-discuss:
>> Check whether there are snapshots on the rpool with zfs list -t snapshot.
>> Sometimes beadm destroy leaves snapshots that have been created (usually 2) for a BE untouched.
>> You can manually destroy them with zfs destroy commands.
>>
>> Andreas
> I checked but there are no snapshots left horphan.
> Instead i launched a 'zfs list' getting this: http://gaox.io/l/d44928b
> Between the forgettable stuff I notoced 'dump', it is really truely forgettable?
> If yes, how can I act over it? Thx
dump is being used for kernel crash dumps. You can read the man page for 
dumpadm(8) for some information.
You seem to have 11 BE's. If you want to increase the free space on the 
device you should destroy some of them.

Andreas
>
> Dan
> 5mode
>
> Oct 4, 2025 19:18:35 Andreas Wacknitz via openindiana-discuss <openindiana-discuss at openindiana.org>:
>
>> Am 04.10.25 um 19:14 schrieb dan via openindiana-discuss:
>>> Hello everyone,
>>>
>>> As per subject I'm dealing with an usual problem, during the pkg update
>>> the pc hanged and after the reboot relaunching the update I continue to get
>>> that there is not enough free space to complete the operation.
>>>
>>> I have already deleted the boot environment and I did a pkg fix just in case.
>>> I'm going though the mail list archive to catch on new ideas but for
>>> now I'm still sticking on the matter.
>>>
>>> My last boot environment is now from 12th September while the free space is around 5.12gb.
>>>
>>> If someone can summarize to me the best proc to fix my station could be
>>> hightly appreciated.
>>>
>>> thx in advance,
>>>
>>> Dan
>>> 5mode
>>>
>>> _______________________________________________
>>> openindiana-discuss mailing list
>>> openindiana-discuss at openindiana.org
>>> https://openindiana.org/mailman/listinfo/openindiana-discuss
>> Check whether there are snapshots on the rpool with zfs list -t snapshot.
>> Sometimes beadm destroy leaves snapshots that have been created (usually 2) for a BE untouched.
>> You can manually destroy them with zfs destroy commands.
>>
>> Andreas
> _______________________________________________
> openindiana-discuss mailing list
> openindiana-discuss at openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss