Hey #NFS / #FreeBSD / #NFS4 experts, I have a weird one.

My file server exports the path:

/common/media to various devices in my house.

All read-only.

There are sub-dirs under it, books, movies, tunes, and cams, plus some junk I have yet to sort. I should note that some of it is owned by nobody:nogroup, some is nuintari:nuintari (for some reason I should clean it up), and the rest is root:wheel, except.....

The clients can see all of this, EXCEPT for cams.

The exports looks like this:

V4: /
/common/media -ro -maproot=root -network 172.16.17.0 -mask 255.255.255.224

There are tons of files under cams, its a syncthing backup for our cellphone's cameras.

The only difference is that the the files in cams come from inside a jail, managed by bastille, where /common/media/cams is mounted inside the jail via nullfs. But even files I create directly in the root filesystem on the server itself, outside the jail are not visible to the clients. This directory and everything under it are all owned by syncthing:syncthing FYI.

Yet every other file under this exact same NFS mount works fine.

Anyone have any ideas? I've been ignoring this for a few weeks now hoping inspiration would hit me. But I got nothing.

Hey #NFS / #FreeBSD / #NFS4 experts, I have a weird one.

My file server exports the path:

/common/media to various devices in my house.

All read-only.

There are sub-dirs under it, books, movies, tunes, and cams, plus some junk I have yet to sort. I should note that some of it is owned by nobody:nogroup, some is nuintari:nuintari (for some reason I should clean it up), and the rest is root:wheel, except.....

The clients can see all of this, EXCEPT for cams.

The exports looks like this:

V4: /
/common/media -ro -maproot=root -network 172.16.17.0 -mask 255.255.255.224

There are tons of files under cams, its a syncthing backup for our cellphone's cameras.

The only difference is that the the files in cams come from inside a jail, managed by bastille, where /common/media/cams is mounted inside the jail via nullfs. But even files I create directly in the root filesystem on the server itself, outside the jail are not visible to the clients. This directory and everything under it are all owned by syncthing:syncthing FYI.

Yet every other file under this exact same NFS mount works fine.

Anyone have any ideas? I've been ignoring this for a few weeks now hoping inspiration would hit me. But I got nothing.

Proxmox fully automated! From ClickOps to Code: Automated. Audited. Revisioned. Repeatable.

Starting from the base by automating:
- Cluster initialization
- Cluster join
- Storage Integration
- Proxmox Backup Server Integration
- SDN Networks (different ones for pros/dev)
- Guest Resources utilizing the cluster infrastructure

#Proxmox#PVE#Pbs#ProxmoxBackupServer #opensource#Automation#Ansible #python #devops #terraform #cicd #pipeline #cluster #nfs #iscsi

https://peertube.gyptazy.com/w/4cp7ddLdSHGSUeUwUPsuo9

Proxmox fully automated! From ClickOps to Code: Automated. Audited. Revisioned. Repeatable.

Starting from the base by automating:
- Cluster initialization
- Cluster join
- Storage Integration
- Proxmox Backup Server Integration
- SDN Networks (different ones for pros/dev)
- Guest Resources utilizing the cluster infrastructure

#Proxmox#PVE#Pbs#ProxmoxBackupServer #opensource#Automation#Ansible #python #devops #terraform #cicd #pipeline #cluster #nfs #iscsi

https://peertube.gyptazy.com/w/4cp7ddLdSHGSUeUwUPsuo9

I don't know if anybody noticed #ZeroFS yet, but it seems there is a completely user space-implementation of #NFS and #blockstorage on top of #S3 #objectstorage: https://github.com/Barre/zerofs

Including a demo running #ZFS on top of it which essentially allows geo-redundant ZFS volumes: https://asciinema.org/a/728234 & https://github.com/Barre/zerofs?tab=readme-ov-file#geo-distributed-storage-with-zfs

I don't see no #FreeBSD port yet, but if that really works it would be absolutely awesome.

#OpenZFS