On 02/21/21 11:43 PM, reader wrote:
I'd like to eventually figure some way to get oi installed on my HP
xw8600
There was a time, A little before build 147 when I was able to install
OI onto this same hardware, and able to run it for several years.
Updating periodically.
A sort of catastrophe
11 TB is about right. Your 2TB disks will be "smaller" by nature of
reporting differences. Much of that is difference between how drive
manufacturers report a megabyte as 1,000,000 bytes and computers report
a megabyte 1048576 bytes.
In a nutshell, in your raidz2 vdev you have eight drives.
I'm not an OS developer (although I have read a fair bit of Solaris etc source
over the years, and have written a kernel module or two for my own amusement).
That said, if you have a core file,
pstack core_file
(whatever the core file's name is) will give a backtrace, which might (although
On February 21, 2021 8:53:44 PM UTC, Toomas Soome via openindiana-discuss
wrote:
>
>
>> On 21. Feb 2021, at 22:50, Reginald Beardsley via openindiana-discuss
> wrote:
>>
>> WTF?
>>
>> I had loads of fun with this 4-5 years ago, but was able to put an
>EFI label on a 3 TB disk and everything
>On Sunday, February 21, 2021, 02:53:48 PM CST, Toomas Soome
>wrote:
>Hipster 2017 is 4 years old, please use current version. If it still is
>dumping core, please file issue/let
>us know.
If the developers/maintainers can't/won't verify this themselves I don't see
much future for
> On Feb 21, 2021, at 16:42, Stephan Althaus
> wrote:
>
> Hello!
>
> The "-s" option does the minimal obvious remove of the corresponding snapshot:
Yes, that does help simplify cleanup; thanks.
___
openindiana-discuss mailing list
I'd like to eventually figure some way to get oi installed on my HP
xw8600
There was a time, A little before build 147 when I was able to install
OI onto this same hardware, and able to run it for several years.
Updating periodically.
A sort of catastrophe happened a few months ago involving
With the exception of perhaps ReFS on Storage Spaces (due to the ability to
have multiple volumes with different redundancies in the same pool), all
CoW filesystem RAID schemes have the same basic *theoretical max* (note the
emphasis) storage calculation equation:
Usable storage, S = (N-p)C,
I've always wondered this, but never had the context to ask until now:
purely out of curiosity (*not* criticism), why does pkg on OI not support pkg
clean or something similar? Or is there a similar OI pkg command I'm
missing? Across all my desktop OSes, I typically clean my package caches
after
Tried to understand a couple of space calculators on line that are
suppoded to show the rough space you end up with using the different
zfs raid configs.
I will have 8 2tb drives that I'd like to run in raidz2.
My usual setup has always been 1 to 1 matching mirrored disks.
So the loss in space
Hello!
The "-s" option does the minimal obvious remove of the corresponding
snapshot:
$ beadm list
BE Active Mountpoint Space Policy Created
openindiana-2020:11:03 - - 42.08M static 2020-11-03 09:30
openindiana-2020:11:26 - -
That doesn‘t work correctly either.
Von meinem iPhone gesendet
> Am 21.02.2021 um 21:43 schrieb Stephan Althaus
> :
>
> On 02/21/21 09:17 AM, Andreas Wacknitz wrote:
>>> Am 21.02.21 um 09:10 schrieb Toomas Soome via openindiana-discuss:
>>>
On 21. Feb 2021, at 08:45, Tim Mooney via
> On 21. Feb 2021, at 22:50, Reginald Beardsley via openindiana-discuss
> wrote:
>
> WTF?
>
> I had loads of fun with this 4-5 years ago, but was able to put an EFI label
> on a 3 TB disk and everything was fine when I moved the disk to my Solaris
> 10 instance where I have two in a
WTF?
I had loads of fun with this 4-5 years ago, but was able to put an EFI label
on a 3 TB disk and everything was fine when I moved the disk to my Solaris 10
instance where I have two in a mirror.
I'm trying to label a 5 TB disk so I can make a backup before attempting to fix
grub on my
On 02/21/21 09:17 AM, Andreas Wacknitz wrote:
Am 21.02.21 um 09:10 schrieb Toomas Soome via openindiana-discuss:
On 21. Feb 2021, at 08:45, Tim Mooney via openindiana-discuss
wrote:
All-
My space-constrained OI hipster build VM is running low on space.
It looks like either pkg caching
While I'm not sure why extra snapshots seem to be involved, here's what I
actually see when going through an update, looking at the results, and cleaning
up.
# starting with just the running BE, no extra snapshots:
root@openindiana:~# pkg update
Packages to install: 10
> On 21. Feb 2021, at 10:17, Andreas Wacknitz wrote:
>
> Am 21.02.21 um 09:10 schrieb Toomas Soome via openindiana-discuss:
>>
>>> On 21. Feb 2021, at 08:45, Tim Mooney via openindiana-discuss
>>> wrote:
>>>
>>>
>>> All-
>>>
>>> My space-constrained OI hipster build VM is running low on
Before you do that, just to cover the obvious, have you gotten rid of old boot
environments (and the snapshots shown with beadm list -a) ?
> On Feb 21, 2021, at 01:45, Tim Mooney via openindiana-discuss
> wrote:
>
>
> All-
>
> My space-constrained OI hipster build VM is running low on
Hi,
We will remove PHP-7.0 and its extensions from OI Hipster soon as its
support ended more than three years ago according to
https://www.php.net/supported-versions.php
Users who haven't migrated to PHP-7.3 yet should do that soon.
Best regards,
Andreas
Am 21.02.21 um 09:10 schrieb Toomas Soome via openindiana-discuss:
On 21. Feb 2021, at 08:45, Tim Mooney via openindiana-discuss
wrote:
All-
My space-constrained OI hipster build VM is running low on space.
It looks like either pkg caching or pkg history is using quite a lot of
space:
$
> On 21. Feb 2021, at 08:45, Tim Mooney via openindiana-discuss
> wrote:
>
>
> All-
>
> My space-constrained OI hipster build VM is running low on space.
>
> It looks like either pkg caching or pkg history is using quite a lot of
> space:
>
> $ pfexec du -ks /var/pkg/* | sort -n
> 0
21 matches
Mail list logo
