[OpenIndiana-discuss] safely cleanup pkg cache?

Richard L. Hamilton rlhamil at smart.net
Sun Feb 21 09:02:19 UTC 2021


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 at openindiana:~# pkg update
           Packages to install:  10
            Packages to update: 377
       Create boot environment: Yes
Create backup boot environment:  No

DOWNLOAD                                PKGS         FILES    XFER (MB)   SPEED
Completed                            387/387     5947/5947  116.2/116.2  617k/s

PHASE                                          ITEMS
Removing old actions                       1139/1139
Installing new actions                     1851/1851
Updating modified actions                  6684/6684
Updating package state database                 Done 
Updating package cache                       377/377 
Updating image state                            Done 
Creating fast lookup database                   Done 

A clone of openindiana-2021:02:20 exists and has been updated and activated.
On the next boot the Boot Environment openindiana-2021:02:21 will be
mounted on '/'.  Reboot when ready to switch to this updated BE.


---------------------------------------------------------------------------
NOTE: Please review release notes posted at:

https://docs.openindiana.org/release-notes/latest-changes/
---------------------------------------------------------------------------

root at openindiana:~# beadm list
BE                     Active Mountpoint Space   Policy Created
openindiana-2021:02:20 N      /          409.50K static 2021-02-20 02:01
openindiana-2021:02:21 R      -          18.03G  static 2021-02-21 03:43
root at openindiana:~# beadm list -a
BE/Dataset/Snapshot                                           Active Mountpoint Space  Policy Created
openindiana-2021:02:20
   rpool1/ROOT/openindiana-2021:02:20                         N      /          409.50K static 2021-02-20 02:01
   rpool1/ROOT/openindiana-2021:02:21 at 2021-02-21-08:43:19     -      -          116K   static 2021-02-21 03:43
   rpool1/ROOT/openindiana-2021:02:21 at 2021-02-21-08:40:01     -      -          1.00M  static 2021-02-21 03:40
   rpool1/ROOT/openindiana-2021:02:21/var at 2021-02-21-08:43:19 -      -          1.43M  static 2021-02-21 03:43
   rpool1/ROOT/openindiana-2021:02:21/var at 2021-02-21-08:40:01 -      -          30.66M static 2021-02-21 03:40
openindiana-2021:02:21
   rpool1/ROOT/openindiana-2021:02:21                         R      -          18.03G static 2021-02-21 03:43
root at openindiana:~# exec shutdown -i6 -y -g0

# after the reboot:

root at openindiana:~# beadm list
BE                     Active Mountpoint Space  Policy Created
openindiana-2021:02:20 -      -          22.53M static 2021-02-20 02:01
openindiana-2021:02:21 NR     /          18.04G static 2021-02-21 03:43
root at openindiana:~# beadm list -a
BE/Dataset/Snapshot                                           Active Mountpoint Space  Policy Created
openindiana-2021:02:20
   rpool1/ROOT/openindiana-2021:02:20                         -      -          22.53M static 2021-02-20 02:01
   rpool1/ROOT/openindiana-2021:02:21 at 2021-02-21-08:43:19     -      -          1.00M  static 2021-02-21 03:43
   rpool1/ROOT/openindiana-2021:02:21 at 2021-02-21-08:40:01     -      -          1.00M  static 2021-02-21 03:40
   rpool1/ROOT/openindiana-2021:02:21/var at 2021-02-21-08:43:19 -      -          1.59M  static 2021-02-21 03:43
   rpool1/ROOT/openindiana-2021:02:21/var at 2021-02-21-08:40:01 -      -          30.66M static 2021-02-21 03:40
openindiana-2021:02:21
   rpool1/ROOT/openindiana-2021:02:21                         NR     /          18.04G static 2021-02-21 03:43

# since it came up, I can probably blow away the old stuff:

root at openindiana:~# beadm destroy openindiana-2021:02:20
Are you sure you want to destroy openindiana-2021:02:20?
This action cannot be undone (y/[n]): y
Destroyed successfully
root at openindiana:~# beadm list -a
BE/Dataset/Snapshot                                           Active Mountpoint Space   Policy Created
openindiana-2021:02:21
   rpool1/ROOT/openindiana-2021:02:21                         NR     /          18.04G  static 2021-02-21 03:43
   rpool1/ROOT/openindiana-2021:02:21/var at 2021-02-21-08:40:01 -      -          350.62M static 2021-02-21 03:40
   rpool1/ROOT/openindiana-2021:02:21 at 2021-02-21-08:40:01     -      -          436.01M static 2021-02-21 03:40
root at openindiana:~# beadm destroy openindiana-2021:02:21 at 2021-02-21-08:40:01
Are you sure you want to destroy openindiana-2021:02:21 at 2021-02-21-08:40:01?
This action cannot be undone (y/[n]): y
Destroyed successfully
root at openindiana:~# beadm list -a
BE/Dataset/Snapshot                   Active Mountpoint Space Policy Created
openindiana-2021:02:21
   rpool1/ROOT/openindiana-2021:02:21 NR     /          17.27G static 2021-02-21 03:43


> On Feb 21, 2021, at 03:17, Andreas Wacknitz <A.Wacknitz at gmx.de> 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 <openindiana-discuss at openindiana.org> 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       /var/pkg/gui_cache
>>> 0       /var/pkg/lock
>>> 0       /var/pkg/modified
>>> 0       /var/pkg/ssl
>>> 6       /var/pkg/pkg5.image
>>> 955     /var/pkg/lost+found
>>> 5557    /var/pkg/history
>>> 23086   /var/pkg/license
>>> 203166  /var/pkg/cache
>>> 241106  /var/pkg/state
>>> 9271692 /var/pkg/publisher
>>> 
>>> What is the correct, safe way to clean up anything from pkg that I don't
>>> need?
>>> 
>>> The closest information I've found is an article from Oracle on "Minimize
>>> Stored Image Metadata":
>>> 
>>> 	https://docs.oracle.com/cd/E53394_01/html/E54739/minvarpkg.html
>>> 
>>> This suggests changing the 'flush-content-cache-on-success' property
>>> to true (OI defaults to False).
>>> 
>>> Is that it, or are there other (generally safe) cleanup steps that I could
>>> take too?  Is 'pkg purge-history' a good idea?
>>> 
>> do not forget to check beadm list -a / zfs list -t snapshot
>> 
>> rgds,
>> toomas
>> 
> I have a question regarding beadm destroy here:
> I do regularly destroy old BEs with "pfexec beadm destroy <BE name>"
> keeping only a handful BEs.
> Checking with "zfs list -t snapshot" shows that this won't destroy most
> (all?) related snapshots, eg. it typically frees only some mb.
> Thus, my rpool is filling over the time and I have to manually destroy
> zfs snapshots that belong to deleted BEs.
> Is that an intentional behavior of beadm destroy and is there something
> how I can enhance on my procedure?
> 
> Regards,
> Andreas
> 
> _______________________________________________
> openindiana-discuss mailing list
> openindiana-discuss at openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
> 



More information about the openindiana-discuss mailing list