Removing or adding snapshot datasets

[silverspr]

Hello....I'm back!!

I don't need the Docker dataset but would like to add a mariadb dataset, so I tried:

starting at line 1247 of the ZFS-root.sh, commented out docker dataset and added two for mariadb....but this doesn't work, the server won't start and goes into emergency state. I thought this would be simple! Then I tried commenting out Docker alone, didn't work either? What am I doing wrong?

if this system will use Docker.....

# turned off docker
#zfs create -o com.sun:auto-snapshot=false -o mountpoint=/var/lib/docker ${POOLNAME}/docker
  zfs create -o com.sun:auto-snapshot=false -o mountpoint=/var/lib/mysql ${POOLNAME}/ROOT/mariadb
  zfs create -o com.sun:auto-snapshot=false -o mountpoint=/var/log/mysql ${POOLNAME}/ROOT/mariadb_logs

I know I can delete and add datasets after the original ZFS-root.sh has run, just thought it would be nice to hardcode into your script. At the very least I would like to be able to comment out the Docker dataset.
thanks again

[Halfwalker]

Hrm - not at home right now but will check next week. Two things ...

• Any particular reason you put the mariadb datasets under ROOT ? That was intended mainly for bootable datasets, though I don't think it will make that much of a difference ?
• You're mounting both datasets to the same dir - you should use different dirs, like /var/lib/mysql and /var/log/mysql_logs
  Be sure to adjust owner/group of the dirs once they're created by the zfs create

[silverspr]

HI thanks for the advice regarding mariadb. That would be my inadequate knowledge of ZFS datasets! I mounted to the directories you mentioned. I presumed because mariadb installs to root that it would be named under the root pool. As for the Docker dataset, commenting it out appears to have worked while I was playing around with setting partition sizes. No need for you to do anything. I might have reached out to you too soon: I'm still trying to learn/understand your script, ZFS as root is new to me also so trying to learn this as well. Will google naming conventions for mariadb under ZFS root. I'm getting ready to move this to production. Thanks again.

[silverspr]

Don't know why or how!! All my modifications worked...sigh! onto production, thanks again for your great work. Your script is a marvel.

NAME USED AVAIL REFER MOUNTPOINT
rpool 2.59G 14.4G 96K none
rpool/ROOT 2.59G 14.4G 96K none
rpool/ROOT/noble 2.59G 14.4G 2.59G /
rpool/ROOT/noble_rescue_base 8K 14.4G 2.59G /
rpool/home 632K 14.4G 96K none
rpool/home/root 144K 14.4G 144K /root
rpool/home/ursa 392K 14.4G 248K /home/ursa
rpool/mariadb 96K 14.4G 96K /var/lib/mysql
rpool/mariadb_logs 96K 14.4G 96K /var/log/mysql

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sr0 11:0 1 1024M 0 rom
nvme0n1 259:0 0 25G 0 disk
├─nvme0n1p1 259:2 0 1000M 0 part
│ └─md127 9:127 0 999.9M 0 raid1 /boot/efi
└─nvme0n1p3 259:3 0 18G 0 part
nvme0n2 259:1 0 25G 0 disk
├─nvme0n2p1 259:4 0 1000M 0 part
│ └─md127 9:127 0 999.9M 0 raid1 /boot/efi
└─nvme0n2p3 259:5 0 18G 0 part

[Halfwalker]

Nice :) Glad it worked out.

I would suggest googling for mysql/mariadb on zfs - there are a few settings to tweak for optimal performance. Recordsize etc.

Also check latest commits - I broke stuff out into functions in an effort to start cleaning it up and making it a bit more modular