Mount point /mnt/mnt/pool1 instead of /mnt/pool1

[stickypt]

Hello All,

After update from RC to FINAL version the mount point of my pool always goes to /mnt/mnt no mather what I do.
Already reinstalled from scratch and happens the same.
Before import the pool I double check the mountpoint of the pool:

> zpool import pool1
> zfs get mountpoint pool1

Result:

NAME PROPERTY VALUE SOURCE
pool1 mountpoint /mnt/pool1 local

> zpool export pool1

Go to GUI, import the pool, then back com shell:

> zfs get mountpoint pool1

Result:
NAME PROPERTY VALUE SOURCE
pool1 mountpoint /mnt/mnt/pool1 local

Tried to change the mount point a lots of times, but it always ends to the same /mnt/mnt point. Samba and other services doesn't work because of mismatch mount point.

 

[Alecmascot]

This may cover it :

auto-import places zvol at /mnt/mnt/zvol instead of /mnt/zvol

Which wouldn't be annoying except the error checking in the GUI won't let me use /mnt/mnt/zvol/filename*** as a file extent mount point in iSCSI.... So my data is there, just not reachable through the GUI... How we got here... Just updated to 8.2 and reloaded my configuration from an earlier...

www.truenas.com

 

[Maximilious]

Sorry for a bump on an old thread but after having this exact issue in SCALE, the proper fix is to run this in the CLI while the pool is mounted:

zfs set mountpoint=/poolname poolname

If you accidentally set the mount to / instead of /poolname it will mount it at the root of /mnt and take precedence over any other pool you may have mounted. You can simply rerun the command with /poolname and your other pools will show up under /mnt again if you make that mistake like I did.

The zfs import/export commands from the other thread do not persist a reboot if you've configured the pool in the web interface. I'm not sure what caused my pool to set an alternate mount point but the above command fixes the issue on the Pool immediately and persists a reboot.

 

[i8degrees]

Many thanks goes out to @Maximilious for posting the answer. This bug has been driving me crazy from time to time, creating such a mess. I don't know what caused it to happen originally with my setup, either, but thank goodness is it now resolved.

Cheers,
Jeff