busybox and nfs mountsSharing Mac Snow Leopard directory via NFSMounting NFS via systemd in Centos 7NFS...
What was the first story to feature the plot "the monsters were human all along"?
Where to draw the line between quantum mechanics theory and its interpretation(s)?
Why did the Apollo 13 crew extend the LM landing gear?
Is any special diet an effective treatment of autism?
Start job from another SQL server instance
Side effects of Initiation by a Guru?
When an imagined world resembles or has similarities with a famous world
Adding command shortcuts to /bin
How should I tell my manager I'm not paying for an optional after work event I'm not going to?
Where are the "shires" in the UK?
What are the advantages of luxury car brands like Acura/Lexus over their sibling non-luxury brands Honda/Toyota?
Is Benjen dead?
Which US defense organization would respond to an invasion like this?
How to pass hash as password to ssh server
How in the world do I place line of text EVENLY between two horizontal tikz lines?
Is it normal for gliders not to have attitude indicators?
Can you use "едать" and "игрывать" in the present and future tenses?
As a GM, is it bad form to ask for a moment to think when improvising?
Dihedral group D4 composition with custom labels
My first c++ game (snake console game)
Why didn't this character get a funeral at the end of Avengers: Endgame?
How do I allocate more memory to an app on Sheepshaver running Mac OS 9?
Can I use a Cat5e cable with an RJ45 and Cat6 port?
Expected Waiting Time in a Queue with exponential distribution
busybox and nfs mounts
Sharing Mac Snow Leopard directory via NFSMounting NFS via systemd in Centos 7NFS mounting options rsize and wsize can't be specified in /etc/fstabError when attempting to mount NFSv4 file systemMount NFS share on notebook (wlan)NFS + Kerberos: access denied by server while mountingNFS mounts getting unmounted, possibly by the kernelLocal file locking on NFS being Linux Kernel dependentMount nfs hangs clientload a file in u-boot over nfs
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
As part of a startup a rescuecd uses busybox to mount a nfs share with data, but during the nfs share mount, busybox (version v1.18.2 from systemrescuecd) always fails to mount the nfs share. And i do not find the reason why, because when using an alternative it works
mount -o intr,nolock,rsize=1024,wsize=1024 192.168.0.3:/rescue /boot
mount: mounting 192.168.0.3:/rescue on /boot failed: Connection timeout
# On the serverside
>> authenticated mount request from 192.168.0.69:642 for /rescue
But here comes the mystery, when i use the following command on the same busybox commandline the nfs mount works (and the server message does NOT appear).
mount.nfs 192.168.0.3:/rescue /boot -o intr,nolock,rsize=1024,wsize=1024
# This works and it is mounted.
What is the difference, who can i make the "normal" mount work on busybox (which is a symlink to busybox)
Otherwise i have to modify the systemrescuecd to make it work. but maybe there is a nfs server tweak just to accept whatever busybox tries to accomplish.
EDIT:
Found out that the mount command is succesful, when the "tcp" option is added.
mount -o intr,nolock,rsize=1024,wsize=1024,tcp 192.168.0.3:/rescue /boot
So the question is more now, why does the mount fail with the "udp" option
mount -o intr,nolock,rsize=1024,wsize=1024,udp 192.168.0.3:/rescue /boot
I am lost here.
nfs busybox system-recovery
asked Jan 1 '18 at 19:13
MandragorMandragor
432416
bumped to the homepage by Community♦ 53 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
As part of a startup a rescuecd uses busybox to mount a nfs share with data, but during the nfs share mount, busybox (version v1.18.2 from systemrescuecd) always fails to mount the nfs share. And i do not find the reason why, because when using an alternative it works
mount -o intr,nolock,rsize=1024,wsize=1024 192.168.0.3:/rescue /boot
mount: mounting 192.168.0.3:/rescue on /boot failed: Connection timeout
# On the serverside
>> authenticated mount request from 192.168.0.69:642 for /rescue
But here comes the mystery, when i use the following command on the same busybox commandline the nfs mount works (and the server message does NOT appear).
mount.nfs 192.168.0.3:/rescue /boot -o intr,nolock,rsize=1024,wsize=1024
# This works and it is mounted.
What is the difference, who can i make the "normal" mount work on busybox (which is a symlink to busybox)
Otherwise i have to modify the systemrescuecd to make it work. but maybe there is a nfs server tweak just to accept whatever busybox tries to accomplish.
EDIT:
Found out that the mount command is succesful, when the "tcp" option is added.
mount -o intr,nolock,rsize=1024,wsize=1024,tcp 192.168.0.3:/rescue /boot
So the question is more now, why does the mount fail with the "udp" option
mount -o intr,nolock,rsize=1024,wsize=1024,udp 192.168.0.3:/rescue /boot
I am lost here.
nfs busybox system-recovery
asked Jan 1 '18 at 19:13
MandragorMandragor
432416
bumped to the homepage by Community♦ 53 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Is youriptablesconfiguration identical in both situations?
– Mark Plotnick
Jan 1 '18 at 20:39
yes it is the very same commandline. Busybox drops after faiure into the commandlline. First command (original one) fails, the second succeeds. I have a further data point, added above
– Mandragor
Jan 2 '18 at 8:15
add a comment |
As part of a startup a rescuecd uses busybox to mount a nfs share with data, but during the nfs share mount, busybox (version v1.18.2 from systemrescuecd) always fails to mount the nfs share. And i do not find the reason why, because when using an alternative it works
mount -o intr,nolock,rsize=1024,wsize=1024 192.168.0.3:/rescue /boot
mount: mounting 192.168.0.3:/rescue on /boot failed: Connection timeout
# On the serverside
>> authenticated mount request from 192.168.0.69:642 for /rescue
But here comes the mystery, when i use the following command on the same busybox commandline the nfs mount works (and the server message does NOT appear).
mount.nfs 192.168.0.3:/rescue /boot -o intr,nolock,rsize=1024,wsize=1024
# This works and it is mounted.
What is the difference, who can i make the "normal" mount work on busybox (which is a symlink to busybox)
Otherwise i have to modify the systemrescuecd to make it work. but maybe there is a nfs server tweak just to accept whatever busybox tries to accomplish.
EDIT:
Found out that the mount command is succesful, when the "tcp" option is added.
mount -o intr,nolock,rsize=1024,wsize=1024,tcp 192.168.0.3:/rescue /boot
So the question is more now, why does the mount fail with the "udp" option
mount -o intr,nolock,rsize=1024,wsize=1024,udp 192.168.0.3:/rescue /boot
I am lost here.
nfs busybox system-recovery
asked Jan 1 '18 at 19:13
MandragorMandragor
432416
As part of a startup a rescuecd uses busybox to mount a nfs share with data, but during the nfs share mount, busybox (version v1.18.2 from systemrescuecd) always fails to mount the nfs share. And i do not find the reason why, because when using an alternative it works
mount -o intr,nolock,rsize=1024,wsize=1024 192.168.0.3:/rescue /boot
mount: mounting 192.168.0.3:/rescue on /boot failed: Connection timeout
# On the serverside
>> authenticated mount request from 192.168.0.69:642 for /rescue
But here comes the mystery, when i use the following command on the same busybox commandline the nfs mount works (and the server message does NOT appear).
mount.nfs 192.168.0.3:/rescue /boot -o intr,nolock,rsize=1024,wsize=1024
# This works and it is mounted.
What is the difference, who can i make the "normal" mount work on busybox (which is a symlink to busybox)
Otherwise i have to modify the systemrescuecd to make it work. but maybe there is a nfs server tweak just to accept whatever busybox tries to accomplish.
EDIT:
Found out that the mount command is succesful, when the "tcp" option is added.
mount -o intr,nolock,rsize=1024,wsize=1024,tcp 192.168.0.3:/rescue /boot
So the question is more now, why does the mount fail with the "udp" option
mount -o intr,nolock,rsize=1024,wsize=1024,udp 192.168.0.3:/rescue /boot
I am lost here.
nfs busybox system-recovery
nfs busybox system-recovery
asked Jan 1 '18 at 19:13
MandragorMandragor
432416
asked Jan 1 '18 at 19:13
MandragorMandragor
432416
edited Jan 2 '18 at 20:18
Mandragor
asked Jan 1 '18 at 19:13
MandragorMandragor
432416
asked Jan 1 '18 at 19:13
MandragorMandragor
432416
asked Jan 1 '18 at 19:13
MandragorMandragor
432416
432416
bumped to the homepage by Community♦ 53 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 53 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Is youriptablesconfiguration identical in both situations?
– Mark Plotnick
Jan 1 '18 at 20:39
yes it is the very same commandline. Busybox drops after faiure into the commandlline. First command (original one) fails, the second succeeds. I have a further data point, added above
– Mandragor
Jan 2 '18 at 8:15
add a comment |
Is youriptablesconfiguration identical in both situations?
– Mark Plotnick
Jan 1 '18 at 20:39
yes it is the very same commandline. Busybox drops after faiure into the commandlline. First command (original one) fails, the second succeeds. I have a further data point, added above
– Mandragor
Jan 2 '18 at 8:15
Is your
iptables configuration identical in both situations?– Mark Plotnick
Jan 1 '18 at 20:39
Is your
iptables configuration identical in both situations?– Mark Plotnick
Jan 1 '18 at 20:39
yes it is the very same commandline. Busybox drops after faiure into the commandlline. First command (original one) fails, the second succeeds. I have a further data point, added above
– Mandragor
Jan 2 '18 at 8:15
yes it is the very same commandline. Busybox drops after faiure into the commandlline. First command (original one) fails, the second succeeds. I have a further data point, added above
– Mandragor
Jan 2 '18 at 8:15
add a comment |
1 Answer
1
active
oldest
votes
You have to enable the nfs server to listen on udp port. This is option -u (see also: man nfsd).
edited Mar 18 '18 at 22:37
Wouter Verhelst
7,609935
answered Mar 18 '18 at 19:41
suilenrocsuilenroc
1
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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%2funix.stackexchange.com%2fquestions%2f414174%2fbusybox-and-nfs-mounts%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
You have to enable the nfs server to listen on udp port. This is option -u (see also: man nfsd).
edited Mar 18 '18 at 22:37
Wouter Verhelst
7,609935
answered Mar 18 '18 at 19:41
suilenrocsuilenroc
1
add a comment |
You have to enable the nfs server to listen on udp port. This is option -u (see also: man nfsd).
edited Mar 18 '18 at 22:37
Wouter Verhelst
7,609935
answered Mar 18 '18 at 19:41
suilenrocsuilenroc
1
add a comment |
You have to enable the nfs server to listen on udp port. This is option -u (see also: man nfsd).
edited Mar 18 '18 at 22:37
Wouter Verhelst
7,609935
answered Mar 18 '18 at 19:41
suilenrocsuilenroc
1
You have to enable the nfs server to listen on udp port. This is option -u (see also: man nfsd).
edited Mar 18 '18 at 22:37
Wouter Verhelst
7,609935
answered Mar 18 '18 at 19:41
suilenrocsuilenroc
1
edited Mar 18 '18 at 22:37
Wouter Verhelst
7,609935
edited Mar 18 '18 at 22:37
Wouter Verhelst
7,609935
edited Mar 18 '18 at 22:37
Wouter Verhelst
7,609935
7,609935
answered Mar 18 '18 at 19:41
suilenrocsuilenroc
1
answered Mar 18 '18 at 19:41
suilenrocsuilenroc
1
answered Mar 18 '18 at 19:41
suilenrocsuilenroc
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- 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%2funix.stackexchange.com%2fquestions%2f414174%2fbusybox-and-nfs-mounts%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
Is your
iptablesconfiguration identical in both situations?– Mark Plotnick
Jan 1 '18 at 20:39
yes it is the very same commandline. Busybox drops after faiure into the commandlline. First command (original one) fails, the second succeeds. I have a further data point, added above
– Mandragor
Jan 2 '18 at 8:15