autofs and NFS failover - can autofs remount?Why are make jobs failing to find dependancies on automounted filesystems?Autofs mount nfs issuesDoes an NFS export with sec=krb5 *require* that the parent directory also be exported with sec=krb5?What are the most common reasons for NFS auto mounts to fail?Autofs redundant failover to local mountpointAutoFS wildcard subdirectorynfs autofs automount of exported filesystems is empty on nfs serverNFS with autofs: mounting /run/lock gives permissions error“Too many levels of symbolic links” in NFS via automount resolved by restarting DockerMonitoring NFS mounts for existence
Best shape for a necromancer's undead minions for battle?
Can a tabaxi rogue with the Criminal background start with 8 skill proficiencies?
Job Market: should one hide their (young) age?
Python program for fibonacci sequence using a recursive function
Why does the Starter Set wizard have six spells in their spellbook?
The disk image is 497GB smaller than the target device
Why do Russians almost not use verbs of possession akin to "have"?
First Program Tic-Tac-Toe
How would a developer who mostly fixed bugs for years at a company call out their contributions in their CV?
Can a ring of spell storing and access to Find spells produce an endless menagerie?
Is there a simple example that empirical evidence is misleading?
One word for 'the thing that attracts me'?
Why would a rational buyer offer to buy with no conditions precedent?
Using too much dialogue?
Why did Jon Snow do this immoral act if he is so honorable?
I want to know what "marumaru" means
The Maltese Falcon
Is superuser the same as root?
How does the Earth's center produce heat?
“For nothing” = “pour rien”?
Shorten or merge multiple lines of `&> /dev/null &`
Why was this character made Grand Maester?
Navigating a quick return to previous employer
Is "vegetable base" a common term in English?
autofs and NFS failover - can autofs remount?
Why are make jobs failing to find dependancies on automounted filesystems?Autofs mount nfs issuesDoes an NFS export with sec=krb5 *require* that the parent directory also be exported with sec=krb5?What are the most common reasons for NFS auto mounts to fail?Autofs redundant failover to local mountpointAutoFS wildcard subdirectorynfs autofs automount of exported filesystems is empty on nfs serverNFS with autofs: mounting /run/lock gives permissions error“Too many levels of symbolic links” in NFS via automount resolved by restarting DockerMonitoring NFS mounts for existence
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
I have this scenario:
2 NFS servers with /usr/share/man as exports (just as example, it can be anything), let say server A and server B (not replicas, just 2 independent servers on the same subnet sharing the same things)
both NFS servers are up and healthy
user is initiating mount from client by executing ls /mnt/usr/man (as example); timeout in auto.master is 2 minutes, fstype=nfs, options=ro,soft
automount is successful, server A was chosen by autofs, and user can see listed man pages
after 1m 10sec server (NFS) A goes down
at 1m 20 sec user executes ls /mnt/usr/man again
What is happening is that it is locked - mount stays on server A and no user can go into /mnt/usr/man (nor lsof is working)
After waiting some minutes (ca 10 minutes)
ls: cannot open directory /mnt/usr/man: Input/output error
My question is: should autofs manage this scenario and automatically remount to server B? (even if mount timeout has not finished yet?)
I have read many articles and it looks like my scenario is not "autofs"'es duty (If I want something like this it should be done another way).
But I want to be sure 100% whether autofs should handle this situation itself or not.
automount autofs
add a comment |
I have this scenario:
2 NFS servers with /usr/share/man as exports (just as example, it can be anything), let say server A and server B (not replicas, just 2 independent servers on the same subnet sharing the same things)
both NFS servers are up and healthy
user is initiating mount from client by executing ls /mnt/usr/man (as example); timeout in auto.master is 2 minutes, fstype=nfs, options=ro,soft
automount is successful, server A was chosen by autofs, and user can see listed man pages
after 1m 10sec server (NFS) A goes down
at 1m 20 sec user executes ls /mnt/usr/man again
What is happening is that it is locked - mount stays on server A and no user can go into /mnt/usr/man (nor lsof is working)
After waiting some minutes (ca 10 minutes)
ls: cannot open directory /mnt/usr/man: Input/output error
My question is: should autofs manage this scenario and automatically remount to server B? (even if mount timeout has not finished yet?)
I have read many articles and it looks like my scenario is not "autofs"'es duty (If I want something like this it should be done another way).
But I want to be sure 100% whether autofs should handle this situation itself or not.
automount autofs
add a comment |
I have this scenario:
2 NFS servers with /usr/share/man as exports (just as example, it can be anything), let say server A and server B (not replicas, just 2 independent servers on the same subnet sharing the same things)
both NFS servers are up and healthy
user is initiating mount from client by executing ls /mnt/usr/man (as example); timeout in auto.master is 2 minutes, fstype=nfs, options=ro,soft
automount is successful, server A was chosen by autofs, and user can see listed man pages
after 1m 10sec server (NFS) A goes down
at 1m 20 sec user executes ls /mnt/usr/man again
What is happening is that it is locked - mount stays on server A and no user can go into /mnt/usr/man (nor lsof is working)
After waiting some minutes (ca 10 minutes)
ls: cannot open directory /mnt/usr/man: Input/output error
My question is: should autofs manage this scenario and automatically remount to server B? (even if mount timeout has not finished yet?)
I have read many articles and it looks like my scenario is not "autofs"'es duty (If I want something like this it should be done another way).
But I want to be sure 100% whether autofs should handle this situation itself or not.
automount autofs
I have this scenario:
2 NFS servers with /usr/share/man as exports (just as example, it can be anything), let say server A and server B (not replicas, just 2 independent servers on the same subnet sharing the same things)
both NFS servers are up and healthy
user is initiating mount from client by executing ls /mnt/usr/man (as example); timeout in auto.master is 2 minutes, fstype=nfs, options=ro,soft
automount is successful, server A was chosen by autofs, and user can see listed man pages
after 1m 10sec server (NFS) A goes down
at 1m 20 sec user executes ls /mnt/usr/man again
What is happening is that it is locked - mount stays on server A and no user can go into /mnt/usr/man (nor lsof is working)
After waiting some minutes (ca 10 minutes)
ls: cannot open directory /mnt/usr/man: Input/output error
My question is: should autofs manage this scenario and automatically remount to server B? (even if mount timeout has not finished yet?)
I have read many articles and it looks like my scenario is not "autofs"'es duty (If I want something like this it should be done another way).
But I want to be sure 100% whether autofs should handle this situation itself or not.
automount autofs
automount autofs
edited Dec 15 '14 at 18:27
HopelessN00b
48.7k25117194
48.7k25117194
asked Jan 13 '14 at 11:45
yusa.viktoryusa.viktor
63
63
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I know this is pretty late to the party, but was the nfs-server service started on server B? I just ran into these exact symptoms, and that was the solution. Try running service nfs-server start
on server B.
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f566885%2fautofs-and-nfs-failover-can-autofs-remount%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I know this is pretty late to the party, but was the nfs-server service started on server B? I just ran into these exact symptoms, and that was the solution. Try running service nfs-server start
on server B.
add a comment |
I know this is pretty late to the party, but was the nfs-server service started on server B? I just ran into these exact symptoms, and that was the solution. Try running service nfs-server start
on server B.
add a comment |
I know this is pretty late to the party, but was the nfs-server service started on server B? I just ran into these exact symptoms, and that was the solution. Try running service nfs-server start
on server B.
I know this is pretty late to the party, but was the nfs-server service started on server B? I just ran into these exact symptoms, and that was the solution. Try running service nfs-server start
on server B.
edited Sep 1 '16 at 15:51
answered Dec 15 '14 at 17:58
aletsonaletson
85
85
add a comment |
add a comment |
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f566885%2fautofs-and-nfs-failover-can-autofs-remount%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown