DAS - NFS alternative to network share HDD

[voarsh]

For the most part I've used USB HDD's and set them up available on NFS on Proxmox.

I technically haven't tried to do the same for my DAS connected HDD, (which I think, probably won't work). Any ideas on how I can get my DAS HDD on a network share on Windows? Someone briefly mentioned Samba to me, but I'm not sure how that's much different from NFS?

(Obviously I'd like to keep using it on the Proxmox host, to be added as mount points on LXC's, etc, as well as a network available drive)

 

[ph0x]

The difference is that Windows works better with Samba than with NFS.
Which connector does the HDD use? As long as your hardware can work with it, you can make it available to/via Proxmox.
Be careful though, simultaneously working on files through different connections is very likely to give you corrupted data.

 

[voarsh]

The difference is that Windows works better with Samba than with NFS.
Which connector does the HDD use? As long as your hardware can work with it, you can make it available to/via Proxmox.
Be careful though, simultaneously working on files through different connections is very likely to give you corrupted data.

I haven't seemingly been able to get the HDD to be NFS share in the datacenter storage area.
It's already added as a directory (the disk). Manually adding the /mnt/pve/hddname to /etc/exports (for NFS) doesn't help share it.

Would Samba be an LXC? If I use a VM and pass through the disk, it won't be usable via Proxmox host itself? (That I am definitely not certain)

The hdd uses SAS connection.

 

[ph0x]

If you add the disk as an NFS storage it will serve Proxmox as a target and not be exported via NFS. Exports you have to manage yourself. But you can of course add the path to /etc/exports. Be sure though, that the package nfs-kernel-server is installed or else this will have nko effect.

You can have Samba run in a container or on the host itself, as you like. If the disk is passed to a container or a VM, the host cannot use in anymore, though. With a bind mount to a container it would still be usable by the host.

 

[voarsh]

You can have Samba run in a container or on the host itself, as you like. If the disk is passed to a container or a VM, the host cannot use in anymore, though. With a bind mount to a container it would still be usable by the host.

Probably I'll try LXC/host for Samba.

If you add the disk as an NFS storage it will serve Proxmox as a target and not be exported via NFS. Exports you have to manage yourself. But you can of course add the path to /etc/exports. Be sure though, that the package nfs-kernel-server is installed or else this will have nko effect.

Yeah, I have NFS setup for other disks, but the disk I want to share over NFS is already added as a directory. Anyway I can do both (keep as a directory and work under NFS)?

 

[ph0x]

The host that serves NFS still has access to the filesystem, yes.
Be aware though that Samba file locking does not work well with other locking mechanisms.
If you work on the same files via Samba and via NFS and/or locally, your data will get corrupted!

 

[voarsh]

If you work on the same files via Samba and via NFS and/or locally, your data will get corrupted!

Not likely to happen - but thanks.

Isn't it easier to remount the disk as a NFS storage backend? (currently it's a directory which explains why NFS exporting a dir isn't working)

 

[ph0x]

Are you sure that we speak about the same thing?
If you add an NFS storage to Proxmox, this means that Proxmox connects to an NFS server in order to read from that storage.
If you add a directory storage than that is a directory on the host which can be used by Proxmox.
If you want your Proxmox host to serve your external disk via NFS to someone else, than you have to take care of that yourself.

Or did you serve the external disk via NFS to the Proxmox host itself? That would be very "creative".