Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement NFS server #24

Open
beikov opened this issue Mar 9, 2020 · 0 comments
Open

Implement NFS server #24

beikov opened this issue Mar 9, 2020 · 0 comments

Comments

@beikov
Copy link
Member

beikov commented Mar 9, 2020

Use https://github.com/dCache/nfs4j for implementing access to buckets through NFS mounts.

We have to think about how to assign "persistent" inode numbers to bucket objects and also to their "virtual directories" as that is what NFS needs to identify objects.

One possible implementation would be to simply not make inodes persistent, but just cache them in memory. This would be ok for uses that only do reads and creates, but even then this could be painful. All clients have to reset their local inode caches after a restart.

A much better implementation would be to allow a global configuration, that when enabled, will maintain a inode number on the bucket_object table based on a sequence through Blazebit/blaze-persistence#365

For directories, we would need a separate table where inodes are managed.

beikov added a commit that referenced this issue Mar 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant