If you use the fstab entry you have specified, then that's exactly what happens - you end up with the directories in the NASData partition appearing under /mnt/nvme02. Any of those directories can then be shared out using an entry in smb.conf, for example:...
I'd like to mount folders from the above partition to folders in, say, the /mnt directory so I end up with mappable folders where [ideally] there is no other limit other than the physical limits of the 1.4Tb partition.
...
Code:
[shareone]path = /mnt/nvme02/firstdirread only = no[sharetwo]path = /mnt/nvme02/seconddirread only = noCode:
[sharethree]path = /mnt/nvme02/firstdir/anotherdirread only = noCode:
[sharefour]path = /mntread only = noyou mean this from the perspective of the client machines - i.e. they're Windows boxes, and you want a mapped drive (U:, V:, W: etc) per category of data. If I've understood you correctly, then the above example should allow you to do this, i.e. a directory in NASData for each category of data, each with it's own share specified in smb.conf.I'd rather have specific mappable drives for each category of data
Statistics: Posted by andrum99 — Sat Aug 09, 2025 12:10 am