Solved [ZFS] adding 2 HDD with different pools to the system

[tuxador]

Hi, I have a desktop with FreeBSD-13.0-BETA3 installed in a SSD, and I recently got 02 HDD attached to extend my storage capacity. I am intending to use theses 500GB HDD for Samba shares.
I did format the 02 HDD's with gpart (GPT), zfs, then create the pools ARCHIVE and DATA:
zfs show gives me this

 pool: archive
 state: ONLINE
status: Some supported features are not enabled on the pool. The pool can
        still be used, but some features are unavailable.
action: Enable all features using 'zpool upgrade'. Once this is done,
        the pool may no longer be accessible by software that does not support
        the features. See zpool-features(5) for details.
config:

        NAME        STATE     READ WRITE CKSUM
        archive     ONLINE       0     0     0
          ada1      ONLINE       0     0     0

errors: No known data errors

  pool: data
 state: ONLINE
status: Some supported features are not enabled on the pool. The pool can
        still be used, but some features are unavailable.
action: Enable all features using 'zpool upgrade'. Once this is done,
        the pool may no longer be accessible by software that does not support
        the features. See zpool-features(5) for details.
config:

        NAME        STATE     READ WRITE CKSUM
        data        ONLINE       0     0     0
          ada2      ONLINE       0     0     0

errors: No known data errors

  pool: zroot
 state: ONLINE
status: Some supported features are not enabled on the pool. The pool can
        still be used, but some features are unavailable.
action: Enable all features using 'zpool upgrade'. Once this is done,
        the pool may no longer be accessible by software that does not support
        the features. See zpool-features(5) for details.
config:

        NAME        STATE     READ WRITE CKSUM
        zroot       ONLINE       0     0     0
          ada0p3    ONLINE       0     0     0

but running gpart show actually shows this

sudo gpart show
Mot de passe :
=>       40  250069600  ada0  GPT  (119G)
         40     409600     1  efi  (200M)
     409640       2008        - free -  (1.0M)
     411648    4194304     2  freebsd-swap  (2.0G)
    4605952  245463040     3  freebsd-zfs  (117G)
  250068992        648        - free -  (324K)

My problem is I cannot access to /archive and /data as a regular user.
What am I missing for a correct configuration of these two volumes ?

 

[SirDice]

zfs show gives me this

That's the output from zpool status you copy/pasted.

My problem is I cannot access to /archive and /data as a regular user.

Are they actually mounted? Then set the correct permissions with chmod(1) and/or chown(8) so your user can access them. This works just like any other directory or mount you added. Normally root:wheel will be the owner and the directory will have 755 permissions. So a user account should be able to read them but cannot write due to the filesystem permissions. Do NOT just blindy set the permissions to 777. Figure out how filesystem permissions actually work, don't fall into the trap of just giving everyone and everything write access.

 

[tuxador]

That's the output from zpool status you copy/pasted.


Are they actually mounted? Then set the correct permissions with chmod(1) and/or chown(8) so your user can access them. This works just like any other directory or mount you added. Normally root:wheel will be the owner and the directory will have 755 permissions. So a user account should be able to read them but cannot write due to the filesystem permissions. Do NOT just blindy set the permissions to 777. Figure out how filesystem permissions actually work, don't fall into the trap of just giving everyone and everything write access.

I will do this tomorrow once in the office.
Do i need to put the option -R to the commands ? both pools are empty for the moment.

 

[tuxador]

changing the rights to 775
chmod -R 775 /archive solved my problem. I was afraid i've overseen some basic step in the process.
Thank you for your help.

 

[SirDice]

I was afraid i've overseen some basic step in the process.

Any new filesystem you mount (doesn't matter if it's ZFS or UFS) will have root:wheel as ownership and have 755 permissions. These are just the default permissions, you need to modify them if you want other users or groups to have write access to that filesystem.

 

[tuxador]

Any new filesystem you mount (doesn't matter if it's ZFS or UFS) will have root:wheel as ownership and have 755 permissions. These are just the default permissions, you need to modify them if you want other users or groups to have write access to that filesystem.

Okay i've just discovered this "feature", so definitively not a "bug" or a mistake from my part. Thank you for the explanation.