/mnt/[directory] re-export problem using derdanne puppet module #129
roscokhan
started this conversation in
Show and tell
Replies: 2 comments
-
Thanks for sharing! |
Beta Was this translation helpful? Give feedback.
0 replies
-
Hi Daniel,
No worries - I guess this is a “corner case”.
On further consideration, it seems that the module uses a single “name space” shared between both the client and server portions, which detects and prevents redeclaration. I was wondering whether separate “name spaces” might also avoid redeclarations.
Many thanks,
Ross
…Sent from my iPhone
On 21 Mar 2021, at 07:34, Daniel Klockenkämper ***@***.***> wrote:
Thanks for sharing!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#129 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AHC7RXYJILKAHEONBI6O2QLTEUBGXANCNFSM4ZQZED5Q>.
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I thought I'd share a solution I found to a duplicate declaration error I experienced when re-exporting some filesystems using derdanne-nfs.
I have an NFS server that I'm using as an aggregation point to mount NFS filesystems from various locations and re-export them to client devices as a single, consolidated mount. This is due to client restrictions (some clients don't handle a mix of ro and rw mounts correctly).
This combination of client and server configurations results in the error (anonymised to protect the innocent):
nfs::client::mount { '/mnt/media/Resources/Presentations':
}
nfs::server::export { '/mnt/media/Resources/Presentations':
}
The error I see:
Error: Could not retrieve catalog from remote server:
Error 500 on SERVER:
Server Error:
Evaluation Error:
Error while evaluating a Resource Statement
Evaluation Error:
Error while evaluating a Resource Statement, Duplicate declaration:
This combination of configurations works as expected:
nfs::client::mount { 'MOUNT_/mnt/media/Resources/Presentations':
}
nfs::server::export { '/mnt/media/Resources/Presentations':
}
I used the string 'MOUNT_' to avoid the naming clash, although I think this could be almost anything, as long as the mount option is specified.
Regards,
Ross
Beta Was this translation helpful? Give feedback.
All reactions