Messages

Thanks for the help. Pretty sure my home use is even lighter than yours. 4GB looks fine. 

I'm running 25.11 as a vm under proxmox. Underlying CPU is a Intel N5105 and the only other VM is running pihole.  I'd appreciate any recommendations on how to configure RAM. I have a 400Mb internet connection.  Heaviest use is a torrent client with many active connections. I stream hulu and share plex with a couple folks but internet usage is generally sub 100Mb.

Currently I've assigned it 4GB and per top it is using 2GB of swap.  Here are the top stats:

Code Select Expand

last pid: 58271;  load averages:  0.15,  0.19,  0.21                                            up 0+02:59:52  19:33:53
65 processes:  1 running, 64 sleeping
CPU:  0.8% user,  0.0% nice,  0.1% system,  0.4% interrupt, 98.8% idle
Mem: 202M Active, 2333M Inact, 467M Laundry, 610M Wired, 393M Buf, 290M Free
ARC:
Swap: 9979M Total, 2063M Used, 7916M Free, 20% Inuse
is the 4GB adequate?  Could it be "too much"?
Could I assign it 2GB and baloonm to 4GB?

Appreciate any thoughts you have.

\\Greg

@gmartin but do not (!) just go ahead and remove the swap partition, then use the procedure outlined by @Maurice. This will lead to a system with no swap at all. Bad idea.

Code Select Expand

root@oprouter:~ # gpart show
=>       40  113246128  da0  GPT  (54G)
         40     532480    1  efi  (260M)
     532520       1024    2  freebsd-boot  (512K)
     533544   49798144    3  freebsd-ufs  (24G)
   50331688   16777136    4  freebsd-swap  (8.0G)
   67108824   46137344       - free -  (22G)


So from the top of my head without any guarantee it will work - go step by step and check the results before proceeding to the next one, please:

Code Select Expand

# make sure secondary GPT header is present
gpart recover da0

# disable swap - take note of the device name, e.g. "/dev/da0p4" or "/dev/gpt/swap"
swapoff -a

# remove swap partition
gpart delete -i 4 da0

# resize UFS partition
gpart resize -i 3 -s 36g da0

# recreate swap partiton - if the device in the first step was "/dev/da0p4" use this:
gpart add -i 4 -t freebsd-swap da0

# recreate swap partition - if the device in the first step was "/dev/gpt/SOMELABEL" use this:
gpart add -i 4 -t freebsd-swap -l SOMELABEL da0

# re-enable swap
swapon -a

If that worked you should have a system with 8 G of swap like before and a resized UFS partition. The last step is to resize the UFS proper.

Connect a console and reboot into single user mode. Do not mount the root partition read/write, just leave it read only (this is the normal state after entering single user mode).

Code Select Expand

fsck -y /
growfs /
df
shutdown -r now

HTH,
Patrick

This is resolved.  Instructions above worked at every step. At first,

Code Select Expand

swapoff -a failed with a "cannot allocste memory" error.  I added memory to the vm and rebooted - then ran swapoff immediately.

Here are the results.

Code Select Expand

root@oprouter:~ # gpart show
=>       40  113246128  da0  GPT  (54G)
         40     532480    1  efi  (260M)
     532520       1024    2  freebsd-boot  (512K)
     533544   96468992    3  freebsd-ufs  (46G)
   97002536   16243632    4  freebsd-swap  (7.7G)

root@oprouter:~ # df
Filesystem                1K-blocks     Used    Avail Capacity  Mounted on
/dev/gpt/rootfs            46707100 11819180 31151352    28%    /
devfs                             1        0        1     0%    /dev
/dev/gpt/efifs               266144     1360   264784     1%    /boot/efi
devfs                             1        0        1     0%    /var/dhcpd/dev
devfs                             1        0        1     0%    /var/unbound/dev
/usr/local/lib/python3.11  46707100 11819180 31151352    28%    /var/unbound/usr/local/lib/python3.11
/lib                       46707100 11819180 31151352    28%    /var/unbound/lib


My only remaining issue is why it filled up to start with. I'll look into log retention config.

Thanks again all.  Happy snow day! (if you live in the US northeast!

Thanks, all. I had read the aforementioned thread and had no luck - so I posted. And now I understand why.  I'm sure there are many repeats here, so I get it.

I'll walk through @patrick's instructions and follow-up when I'm done.

\\Greg

I'm running 25.1.12 in a VM on proxmox v9. It's been running about 9 months without issue.  I noticed today the drive was full.  In the proxmox console, I increased the disk space to 50GB.  I was prompted in the console to run a command to accept the growth but it did not expand the file system. 
The system is showing a discrepancy between gpart and df.

I assume there is something I need to do inside to grow the fs, but growpart isn't available. Is there another tool?

(BTW, I deleted some logs to alleviate the immediate issue.)

Thanks!

Code Select Expand

root@oprouter:~ # df -h
Filesystem                   Size    Used   Avail Capacity  Mounted on
/dev/gpt/rootfs               23G     11G     10G    50%    /
devfs                        1.0K      0B    1.0K     0%    /dev
/dev/gpt/efifs               260M    1.3M    259M     1%    /boot/efi
devfs                        1.0K      0B    1.0K     0%    /var/dhcpd/dev
devfs                        1.0K      0B    1.0K     0%    /var/unbound/dev
/usr/local/lib/python3.11     23G     11G     10G    50%    /var/unbound/usr/local/lib/python3.11
/lib                          23G     11G     10G    50%    /var/unbound/lib
and

Code Select Expand

root@oprouter:~ # gpart show
=>       40  113246128  da0  GPT  (54G)
         40     532480    1  efi  (260M)
     532520       1024    2  freebsd-boot  (512K)
     533544   49798144    3  freebsd-ufs  (24G)
   50331688   16777136    4  freebsd-swap  (8.0G)
   67108824   46137344       - free -  (22G)



I'm having a similar issue. New opnSense install and it appears the dhcpv6 is handing out the router ip as the DNS. I need it to be the pihole ipv6.  How does one edit the config file?