Solved New ZFS-mountpoints after updates?

  • Thread starter Deleted member 43773
  • Start date
D

Deleted member 43773

Guest
(Would this had been better posted under /storage/ZFS?)

After updates my zfs list shows new mountpoints/fs(?)
"*-p2_2022-11-06_*" etc.):

Code: 
root-pool                                         38.2G   171G       96K  /root-pool
root-pool/ROOT                                    35.9G   171G       96K  none
root-pool/ROOT/13.1-RELEASE-p2_2022-11-06_142413     8K   171G     19.9G  /
root-pool/ROOT/13.1-RELEASE-p3_2022-12-03_094943     8K   171G     21.0G  /
root-pool/ROOT/13.1-RELEASE_2022-09-01_160420        8K   171G     24.9G  /
root-pool/ROOT/default                            35.9G   171G     20.0G  /
root-pool/usr                                     2.27G   171G       96K  /usr
root-pool/usr/ports                               1.52G   171G     1.52G  /usr/ports
root-pool/usr/src                                  765M   171G      764M  /usr/src
root-pool/var                                     6.50M   171G       96K  /var
root-pool/var/audit                                 96K   171G       96K  /var/audit
root-pool/var/crash                                 96K   171G       96K  /var/crash
root-pool/var/log                                 4.79M   171G     1.24M  /var/log
root-pool/var/mail                                1.26M   171G      268K  /var/mail
root-pool/var/tmp                                  176K   171G       96K  /var/tmp

As I pulled myself together (jumped to conclusions) those contain the according informations of done updates (links?), cause with 8k they cannot contain much.

My question:
Are those permanent ("forever")?
Are they removed again one day, such by an major upgrade (13 > 14)?
I mean if everytime an upgrade is installed and I get one... at FreeBSD 20 or so I'll may get a (very) long list of those.

Or are those be a sign something was not done smoothly on my machine?


Thank you guys for explanations
and links to where I could read more about it.
 
If you are using "root on ZFS" (which it looks like you are), when you run freebsd-update it creates a new Boot Environment (BE) for you.
I'm assuming that you are actually in the BE named default (output of bectl list will confirm that), so the other BE's represent the system prior to an update.

Are they permanent? Yes, unless you explicitly remove them with the command bectl destroy -o 13.1-RELEASE-p2_2022-11-06_142413 (repeat for each BE you don't want)

Are they removed again....? I don't think they are automatically removed, you have to manually remove them.

Before you do anything, if you post the output of
bectl list

that will let everyone confirm what you have.

For reading, if you search in the forums for freebsd-update zfs boot environment you should find a bunch more information.
 
zirias@ said:
I wasn't aware this is on by default
Click to expand...
I'm not exactly sure when it became default, but I think roughly sometime after 13.0-RELEASE and 13.1-RELEASE (maybe early in 13.1 releases).
Took me by surprise but since I usually create a new BE when updating, it saves me a step but adds one because I have to use bectl to rename things (instead of simply creating one with my desired name).
 
Thanks guys!

That cleared up most and gave me hints to dig deeper.

It has to be on by default, 'cause I didn't change anything about my freebsd-update.conf.
As far as I observed it came up with 13.0.
With <=12* I didn't saw it before, it's new to me, that's why I asked.
Code: 
#bectl list

BE                                Active Mountpoint Space Created
13.1-RELEASE-p2_2022-11-06_142413 -      -          1.73G 2022-11-06 14:24
13.1-RELEASE-p3_2022-12-03_094943 -      -          2.38M 2022-12-03 09:49
13.1-RELEASE_2022-09-01_160420    -      -          6.70G 2022-09-01 16:04
default                           NR     /          35.9G 2022-04-06 11:59

So, bottom line:
Those are Boot Environments,
capable to fallback to former versions,
no need to remove them - "feeds no bread" as we say.

If (too) many (old/obsolete versions) occur, remove with bectl.

Thanks a lot!
 
No need to remove them, I tend to have "the one I'm currently using and the one previous" that way if I do anything stupid in the current one, I can reboot, rollback 1, and work on fixing my mistake.
Take some time reading the man page for bectl you can do a lot of neat things with it, like mount a boot environment somewhere which lets you go fix config files.
 
I don't want to remove them (yet).
I did once on my experimenting machine by brute force - deleting this mountpoint.
Not a good idea (don't do this at home!) 😂

I just wondered how long the list is gonna be after... 20..30 updates?
Because of my MS Windows experience I'm like a bit allergic about my machine getting trashed up...

Okay, I understand it could make sense one day (if there would be >5) to remove the oldest ones,
(They are independently, not needing each other?)
because I don't think I will get into a situation where I need to fall back from e.g. 15.4-p6 to 13.0-p2 :cool:

Thanks again.
 
You must log in or register to reply here.
Back
Top