thanks for the hint, i did
On Wed, 17 Jan 2024 16:35:52 -0800, Bill Sommerfeld via openindiana-discuss
wrote:
> If you want to dig into what's going on I'd look carefully at the code
> in libbe (usr/src/lib/libbe/common/*)
___
openindiana-discuss
thanks for the confirmation. filed: https://www.illumos.org/issues/16196
On Thu, 18 Jan 2024 22:45:36 +0100, Marcel Telka wrote:
> Even 'beadm create NEWBE' is enough to reproduce the issue (just tried).
> Feel free to file a bug report here:
>
>
On Thu, Jan 18, 2024 at 01:22:42AM +0100, Goetz T. Fischer wrote:
> On Wed, 17 Jan 2024 14:34:59 +0100, Marcel Telka wrote:
> > On Wed, Jan 17, 2024 at 08:01:22AM +0100, Goetz T. Fischer wrote:
> >> however, the catch was that the new be, that's created during a "pkg
> >> update", doesn't keep
On Thu, 18 Jan 2024 01:22:42 +0100, Goetz T. Fischer wrote:
> On Wed, 17 Jan 2024 14:34:59 +0100, Marcel Telka wrote:
>> On Wed, Jan 17, 2024 at 08:01:22AM +0100, Goetz T. Fischer wrote:
>>> however, the catch was that the new be, that's created during a "pkg
>>> update", doesn't keep the
>>>
On 1/17/24 16:22, Goetz T. Fischer wrote:
On Wed, 17 Jan 2024 14:34:59 +0100, Marcel Telka wrote:
On Wed, Jan 17, 2024 at 08:01:22AM +0100, Goetz T. Fischer wrote:
however, the catch was that the new be, that's created during a "pkg update",
doesn't keep the
compression setting. after the
On Wed, 17 Jan 2024 14:34:59 +0100, Marcel Telka wrote:
> On Wed, Jan 17, 2024 at 08:01:22AM +0100, Goetz T. Fischer wrote:
>> however, the catch was that the new be, that's created during a "pkg
>> update", doesn't keep the
>> compression setting. after the reboot i noticed that the new /var had
On Wed, Jan 17, 2024 at 08:01:22AM +0100, Goetz T. Fischer wrote:
> however, the catch was that the new be, that's created during a "pkg update",
> doesn't keep the
> compression setting. after the reboot i noticed that the new /var had
> compression set to off again and
> therefore was big
hi again,
to tame the space hunger of /var/pkg a little, i turned zfs compression on for
the /var filesystem. then
i ran "pkg refresh --full" and voila, /var had not even half of its previous
size anymore. so that
worked great.
however, the catch was that the new be, that's created during a
