Why does my pool have the immutable attribute set?

[sheps]

I recently tried to create a top-level dataset in my first pool and ran into a permission issue. It appears, similar to this thread, that my pool was somehow marked as immutable at one point. I know how to change the attribute. However, I don't understand how or why the immutable attribute appeared. Can someone elucidate?

Code:

admin@truenas[~]$ lsattr /mnt/
----i----------------- /mnt/coolpool
---------------------- /mnt/dualpool

 

[anodos]

Immutable is by default set on dataset / pool mountpoints to prevent users from writing under them if they are encrypted + locked or otherwise unmouted. df -T /mnt/coolpool will tell you what filesystem is actually mounted there.

 

[sheps]

Thanks, that makes sense.

All my datasets are unlocked. Looks like the root pool dataset is mounted, too. Not sure when the attribute was set on my end, then. Is it alright to run chattr -i /mnt/coolpool?

Code:

admin@truenas[~]$ df -T /mnt/coolpool
Filesystem     Type   1K-blocks  Used   Available Use% Mounted on
coolpool       zfs  34632087808   512 34632087296   1% /mnt/coolpool

I assume the 512 used is just from the actual root dataset, because I do have several child datasets with about 5TB of storage at this point.