hmmm... where did that idea come from? do you have a good link to a more detailed explanation?
hmmm... where did that idea come from? do you have a good link to a more detailed explanation?
AFAIK, this is not possible with ZFS. Recently, I had to increase my swap space from 8GB to 32GB to build editors/vscode successfully by taking a full recursive snapshot of my zroot and sending it to my storage drives, then reduce root partition's size and add them back to swap space and restore zroot. I don't think that you can resize ZFS partitions.Just install with ZFS next time. No need to bother with partitions, and you can adjust size limits at any time. I discovered that kind of convenience back in 2017!
Hmm, for me was enough swapoff, then destroy swap zvol and create new bigger swap zvol + reboot.
I have a seperate freebsd-swap partition in my root disk. I heard that swap on ZFS is a bad idea but don't know why.
% gpart show -p nda0
=> 40 500118112 nda0 GPT (238G)
40 532480 nda0p1 efi (260M)
532520 67108864 nda0p2 freebsd-swap (32G)
67641384 432476768 nda0p3 freebsd-zfs (206G)I forgot all about partitioning the disk since moving to ZFS... One less installation-related headache, more flexibility later on, what's not to like? No-brainer for me. Oh, and by default, my swap size is just 2 GB, and I compiled my way into KDE 6 on that setup no problem.
% gpart show
=> 40 1000215136 nda0 GPT (477G)
40 532480 1 efi (260M)
532520 1024 2 freebsd-boot (512K)
533544 984 - free - (492K)
534528 4194304 3 freebsd-swap (2.0G)
4728832 995485696 4 freebsd-zfs (475G)
1000214528 648 - free - (324K)How much system memory do you have? I didn't have compilation issues with big ports like llvm, rust, electron, firefox etc. but vscode does requires more ram and i had less swap back then and it failed to build. I have 16GB of ram.
Hello astylehmmm... where did that idea come from? do you have a good link to a more detailed explanation?
Thanks. 13.0-RELEASE is EoL, though. Good thing that archived copies of documentation still exist. But I would suggest making sure to check against the up-to-date stuff, especially if you're running up-to-date stuff yourself:
I have 40 GB RAM on the system I was using for this conversation. However, I have compiled same stuff in VMs that got 16GB of RAM, and 2 GB of swap in a ZFS setup.
with ZFS, you don't need to bother with partitions at all.
Well, the Handbook section 14.7.2. Creating a Swap File, does have a warning that says that while it's not impossible to add swap space as a ZFS dataset, it can lead to system hangs... I haven't researched beyond that piece of info.
So you are using ZFS without any partition, I mean did you give your whole disk to the ZFS? I think that it can create problems with partition table.
Yes, the installer creates the partitions for you.
I see, did you ever built editors/vscode with 16GB ram ? I think 40GB is more than enough. Some big ports can still build in less ram but vscode seems to be kind of different with it's heavy swap usage in 16gb or less systems.
Never had a problem
. I sure did give the whole disk to ZFS, that's what it takes to get the friggin' awesome flexibility that won me over and got me to forget about partitioning headaches. Well, I ditched platter-based disks back in 2012, and used only SSDs ever since.