Running zfs list -r usb_backup, doesn’t the output show the mountpoint there?
NAME USED AVAIL REFER MOUNTPOINT
usb_backup 306G 140G 288K /test/usb_backup
Yeah, I was thinking of mounting to test rather than test/usb_backup but it looks like it adds that automatically. Sorry.
Ah, it was good idea to test out nonetheless. Thanks for the suggestion!
After you import the pool, run zfs list
I get the same output as “zfs list -r usb_backup”
NAME USED AVAIL REFER MOUNTPOINT
usb_backup 306G 140G 288K /test/usb_backup
Please show us the output of df -T with the pool imported.
- Confirming pool is imported with “zfs list -r usb_backup”
NAME USED AVAIL REFER MOUNTPOINT
usb_backup 306G 140G 288K /mnt/usb_backup
- Output of “df -T”
Filesystem Type 1K-blocks Used Available Use% Mounted on
/dev/nvme0n1p2 ext4 1920688992 397766644 1425282896 22% /
devtmpfs devtmpfs 15946996 0 15946996 0% /dev
tmpfs tmpfs 15965312 697868 15267444 5% /dev/shm
efivarfs efivarfs 128 61 63 50% /sys/firmware/efi/efivars
tmpfs tmpfs 6386128 2332 6383796 1% /run
none tmpfs 1024 0 1024 0% /run/credentials/systemd-journald.service
tmpfs tmpfs 15965312 12404 15952908 1% /tmp
/dev/nvme1n1p1 ext4 1921724608 80001088 1744031464 5% /mnt/83f41a0b-854b-46bb-9c74-99b964d472a8
/dev/nvme0n1p1 vfat 1046512 288 1046224 1% /boot/efi
tmpfs tmpfs 3193060 172 3192888 1% /run/user/1000
Show us the properties of the dataset with:
zfs get all usb_backup
Not be rude but who gives someone a USB stick with zfs on it? I love zfs and use it all over the place but it requires knowledge. It isn’t the filesystem I would use for transferring data to a 3rd party.
That being said, I also would like to see the output that @mbod is requesting so we can see if that dataset is encrypted and what the mount options are on it.
Not only that, but computerhelp said
If your friend is using you as an `off-site backup for the important things’, should you be poking around in his data. Maybe he gave you the thumb drive in ZFS to keep anyone from snooping around.
Pudge
3 Likes
Check out his dirty videos collection 
1 Like
That gives out a lot of output, but here is “zfs get all usb_backup”
NAME PROPERTY VALUE SOURCE
usb_backup type filesystem -
usb_backup creation Mon Dec 22 13:33 2025 -
usb_backup used 306G -
usb_backup available 140G -
usb_backup referenced 288K -
usb_backup compressratio 1.02x -
usb_backup mounted no -
usb_backup quota none default
usb_backup reservation none default
usb_backup recordsize 128K default
usb_backup mountpoint /mnt/usb_backup default
usb_backup sharenfs off default
usb_backup checksum on default
usb_backup compression lz4 local
usb_backup atime off local
usb_backup devices on default
usb_backup exec on default
usb_backup setuid on default
usb_backup readonly off default
usb_backup zoned off default
usb_backup snapdir hidden default
usb_backup aclmode discard local
usb_backup aclinherit passthrough local
usb_backup createtxg 1 -
usb_backup canmount on default
usb_backup xattr sa local
usb_backup copies 1 default
usb_backup version 5 -
usb_backup utf8only off -
usb_backup normalization none -
usb_backup casesensitivity sensitive -
usb_backup vscan off default
usb_backup nbmand off default
usb_backup sharesmb off default
usb_backup refquota none default
usb_backup refreservation none default
usb_backup guid 17716103189138815685 -
usb_backup primarycache all default
usb_backup secondarycache all default
usb_backup usedbysnapshots 0B -
usb_backup usedbydataset 288K -
usb_backup usedbychildren 306G -
usb_backup usedbyrefreservation 0B -
usb_backup logbias latency default
usb_backup objsetid 54 -
usb_backup dedup off default
usb_backup mlslabel none default
usb_backup sync standard default
usb_backup dnodesize legacy default
usb_backup refcompressratio 1.00x -
usb_backup written 288K -
usb_backup logicalused 312G -
usb_backup logicalreferenced 104K -
usb_backup volmode default default
usb_backup filesystem_limit none default
usb_backup snapshot_limit none default
usb_backup filesystem_count none default
usb_backup snapshot_count none default
usb_backup snapdev hidden default
usb_backup acltype posix local
usb_backup context none default
usb_backup fscontext none default
usb_backup defcontext none default
usb_backup rootcontext none default
usb_backup relatime on default
usb_backup redundant_metadata all default
usb_backup overlay on default
usb_backup encryption aes-256-gcm -
usb_backup keylocation prompt local
usb_backup keyformat hex -
usb_backup pbkdf2iters 0 default
usb_backup encryptionroot usb_backup -
usb_backup keystatus unavailable -
usb_backup special_small_blocks 0 default
usb_backup prefetch all default
usb_backup direct standard default
usb_backup longname off default
usb_backup defaultuserquota 0 -
usb_backup defaultgroupquota 0 -
usb_backup defaultprojectquota 0 -
usb_backup defaultuserobjquota 0 -
usb_backup defaultgroupobjquota 0 -
usb_backup defaultprojectobjquota 0 -
That’s exactly what i thought when i started to read this topic this morning. Just format the drive and stop poking around.
Maybe you’re right, but this is the first time we’re experimenting with Truenas. Mistakes will be made (this possibly being one of them)
It is encrypted. You need to unlock it with the encryption key before it will mount.
If you know the password, you can use:
zfs load-key usb_backup
So perhaps there’s a playful element to this comment, but it does come off as rather cynical.
He gave me his thumb drive with the intention of copying it to my computer. I can’t convince you of that in anyway, and if you feel my intentions are malicious, by all means don’t help.
I don’t know, after having so much troulbe just mounting a file system, this comment left a really sour taste in my mouth. Again maybe you’re being playful, but it really doesn’t carry over in text.
Ahh… that could be it. Can it not be mounted without decrypting?
I specifically told him to encrypt it for his ease of mind.
If it can’t, then we will do offsite backup another way
No, that would defeat the purpose of the encryption.
You need the password to access the volume.
Got it. In my mind, encryption would function like a blob of data just inaccessible. LIke I can still copy it, but I can’t read it
Clearly I was wrong in that assumption.
We will back it up another way (maybe a simple zip encryption)
If you don’t mind, just as an excercise in completeness, I will get the encryption key and try to mount it tomorrow or something.
So for the sake of completeness, I need to first: decrypt it via: zfs load-key usb_backup
Will it mount automatically after that? Or do I need to run “zpool import -R /mnt usb_backup” afterwards?
Decrypt first and then import pool? Or Import pool first and then decrypt?
It may mount since it looks like the data is at the root level. If not, you can use zfs mount usb_backup