2:45 p.m.
Can anyone explain this? How can it be fixed? Do some services need to
be started on the server?
The server is "weather". This log is from the client:
# mount -t nfs weather:/home/jonrysh /mnt/weather
# ls /mnt/weather
Desktop Documents Downloads Music Pictures Public Templates Videos grub2
# umount /mnt/weather
# mount -t nfs4 weather:/home/jonrysh /mnt/weather
mount.nfs4: mounting weather:/home/jonrysh failed, reason given by server:
No such file or directory
#
Thanks in advance - jon
4:01 p.m.
partition? usually problems are among some of these files: exports
file, iptables, sysconifg/nfs
On 26 April 2012 21:59, Joe Zeff <joe(a)zeff.us> wrote:
On 04/26/2012 12:45 PM, Jonathan Ryshpan wrote:
>
> Thanks in advance - jon
I'll admit that I don't know much about this, but it might help to know how
that partition's formatted. It might make a difference in how it gets
mounted.
--
users mailing list
users(a)lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
4:38 p.m.
On 04/26/2012 02:01 PM, Kernel Guardian wrote:
partition? usually problems are among some of these files: exports
file, iptables, sysconifg/nfs
My thought was that you probably couldn't mount it as ntfs4 if it were
formatted as ntfs3. Again, just trying to eliminate an unlikely
possibility.
4:54 p.m.
nfs stands from network file system. Although you can export almost
any file system over nfs.
http://en.wikipedia.org/wiki/Network_File_System_%28protocol%29
it is impossible to format any disk partition as any type of nfs.
On 26 April 2012 23:38, Joe Zeff <joe(a)zeff.us> wrote:
On 04/26/2012 02:01 PM, Kernel Guardian wrote:
>
> partition? usually problems are among some of these files: exports
> file, iptables, sysconifg/nfs
My thought was that you probably couldn't mount it as ntfs4 if it were
formatted as ntfs3. Again, just trying to eliminate an unlikely
possibility.
--
users mailing list
users(a)lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
3:17 p.m.
New subject: mount -t nfs4 fails, but mount -t nfs succeeds [SOLVED]
On Thu, 2012-04-26 at 12:45 -0700, Jonathan Ryshpan wrote:
Can anyone explain this? How can it be fixed? Do some services need
to
be started on the server?
The server is "weather". This log is from the client:
# mount -t nfs weather:/home/jonrysh /mnt/weather
# ls /mnt/weather
Desktop Documents Downloads Music Pictures Public Templates Videos grub2
# umount /mnt/weather
# mount -t nfs4 weather:/home/jonrysh /mnt/weather
mount.nfs4: mounting weather:/home/jonrysh failed, reason given by server:
No such file or directory
#
Following a suggestion in the Arch Linux Wiki:
https://wiki.archlinux.org/index.php/NFSv4#Exports
I made this minor edit to /etc/exports on weather (the server)
Old /etc/exports:
/ amito(rw,no_root_squash)
/home/jonrysh amito(rw,no_root_squash)
New /etc/exports:
/ amito(rw,fsid=0,no_root_squash)
/home/jonrysh amito(rw,no_root_squash)
Note that the addition of "fsid=0" to the entry for the root directory
allows *both* the root and a directory under it to be exported. To
understand this better, read the following section in the Arch Linux
Wiki: Exporting directories outside your NFS root
All very subtle, and undocumented.
jon
4:59 p.m.
New subject: mount -t nfs4 fails, but mount -t nfs succeeds [SOLVED]
Jonathan Ryshpan wrote:
All very subtle, and undocumented.
$ man exports
/fsid[ENTER]
It is documented. You must understand that NFSv3 and NFSv4 are different
in many ways.
P.S. I'm not sure why you want to export the entire file system when you
are not mounting it on the remote end. Your "/" line could be removed.
7:47 p.m.
New subject: mount -t nfs4 fails, but mount -t nfs succeeds [SOLVED]
On Thu, 2012-04-26 at 16:59 -0500, Michael Cronenworth wrote:
P.S. I'm not sure why you want to export the entire file system
when
you are not mounting it on the remote end. Your "/" line could be
removed.
It's usually not advised to share the whole file system, particularly
over an unsecure scheme. But if you are (as they were), then it becomes
redundant to also share out directories inside it, particularly if
you're not trying to share them out with different options set (and
they're not).
--
[tim@localhost ~]$ uname -r
2.6.27.25-78.2.56.fc9.i686
Don't send private replies to my address, the mailbox is ignored. I
read messages from the public lists.
2:57 a.m.
New subject: mount -t nfs4 fails, but mount -t nfs succeeds [SOLVED]
On Thu, 2012-04-26 at 13:17 -0700, Jonathan Ryshpan wrote:
On Thu, 2012-04-26 at 12:45 -0700, Jonathan Ryshpan wrote:
> Can anyone explain this? How can it be fixed? Do some services need to
> be started on the server?
>
> The server is "weather". This log is from the client:
> # mount -t nfs weather:/home/jonrysh /mnt/weather
> # ls /mnt/weather
> Desktop Documents Downloads Music Pictures Public Templates Videos
grub2
> # umount /mnt/weather
> # mount -t nfs4 weather:/home/jonrysh /mnt/weather
> mount.nfs4: mounting weather:/home/jonrysh failed, reason given by server:
> No such file or directory
> #
Following a suggestion in the Arch Linux Wiki:
https://wiki.archlinux.org/index.php/NFSv4#Exports
I made this minor edit to /etc/exports on weather (the server)
Old /etc/exports:
/ amito(rw,no_root_squash)
/home/jonrysh amito(rw,no_root_squash)
New /etc/exports:
/ amito(rw,fsid=0,no_root_squash)
/home/jonrysh amito(rw,no_root_squash)
Note that the addition of "fsid=0" to the entry for the root directory
allows *both* the root and a directory under it to be exported. To
understand this better, read the following section in the Arch Linux
Wiki: Exporting directories outside your NFS root
All very subtle, and undocumented.
What a lot of comments! This deserves a reply at length. I state a lot
of things below as fact. But snce I'm still pretty ignorant about nfs4
some of them may not be true. Those who know please put in corrections;
and we may arrive at the truth about something that's still pretty murky
to most people. Comments on particular postings follow.
Nfs4 exports a tree of directories from a server to a client. The root
of the tree must be the root of the filesystem on the host and the
line containing it in /etc/exports must contain the option fsid=root
(alternately fsid=0). If such a line appears in /etc/exports then any
directory on the server can be exported, and the client can mount any
directory appearing there. Nfs4 works through a firewall, provided
that port port 2049/tcp is opened; nfs3 requires that the firewall be
(completely) disabled. "showmount -e <host>" doesn't work through a
firewall, it appears to be associated with nfs3. There is no utility
like it that works through port 2049/tcp; administrators have to know
which files are available via the nfs4 port from which servers.
There's an intro to setting up nfs4 (link from Ed Greshko) that states
that the fsid=0 option can be applied to any directory, and then other
directories to be exported should be (bound to) subdirectories of this
one; but I haven't been able to get it to work. Funky problems:
1) If the client has an actual name or exact IP address in /etc/exports,
like this line:
/nfs4 amito:/(rw,fsid=0,...)
or
/nfs4 192.168.2.5(rw,fsid=0,...)
mount attempts fail with the message "No such file or directory".
2)If the line in /etc/exports has a form like
/nfs4 192.168.0.0/24(rw,fsid=0,...)
mount attempts fail with the message "access denied by server".
There's probably some problem with the options in the parentheses,
but I've tried them all, starting with the exact ones in the intro
without success. On the other hand, exporting the actual root
/ amito:(rw,fsid=0,..)
mounts fine.
I hope to be enlightened.
Detailed comments follow:
Michael Cronenworth <mike(a)cchtml.com> wrote
Jonathan Ryshpan wrote:
> All very subtle, and undocumented.
$ man exports
/fsid[ENTER]
It is documented. You must understand that NFSv3 and NFSv4 are different
in many ways.
So it is, in a sense. But the documentation of fsid in the exports man
page isn't marked as having anything in particular to do with nfs4.
P.S. I'm not sure why you want to export the entire file system
when you
are not mounting it on the remote end. Your "/" line could be removed.
Quite right. But I didn't want to let exporting the root filesystem be
a red herring.
Veli-Pekka Kestilä <fedora(a)guagua.fi> wrote
On 26.4.2012 22:45, Jonathan Ryshpan wrote:
> ...
Could you post your /etc/exports from "weather" as the exports syntax is
different for nfs3 and nfs4.
The exports *syntax* is the same in nfs4 as in nfs3. There are
differences in *semantics* as I explained in my note at the start of
this posting.
Ian Pilcher <arequipeno(a)gmail.com> wrote
On 04/26/2012 02:45 PM, Jonathan Ryshpan wrote:
...
NFSv4 works very differently from previous versions. You should be able
to Google up plenty of documentation.
If only... I spent most of a day Googling around before I found the
article in the Arch Linux Wiki. Most of the stuff in my note at the
top doesn't seem to be anywhere obvious.
Robert P. J. Day <rpjday(a)crashcourse.ca> wrote
...
possibly off-topic but a long, long, *long* time ago, i wondered if
you could set up a network using *exclusively* NFSv4, and found it was
impossible -- at least one of the client programs required some
earlier version of NFS even if it wasn't being used.
any clarification on whether one can run a *purely* NFSv4 network?
The example network, though a very small one (2 machines) run nfs4 only.
Ed Greshko <Ed.Greshko(a)greshko.com> wrote
...
When working with NFSv4 I sometimes consult this for reference....
http://www.crazysquirrel.com/computing/debian/servers/setting-up-nfs4.jspx
Very good reference.
Kernel Guardian <kernelgardian(a)gmail.com> wrote:
...
what version of Fedora you use? (nfs server / nfs client)
can you attach /etc/exports and /etc/syconfig/nfs files?
can you attach /etc/sysconfig/iptables?
> All of these files are from nfs server side.
Both systems are running Fedora-16 with all upgrades installed.
Unfortunately I have made so many changes to /etc/exports and the firewall
on the server that these would not be useful.
3:10 a.m.
New subject: mount -t nfs4 fails, but mount -t nfs succeeds [SOLVED]
On 04/27/2012 03:57 PM, Jonathan Ryshpan wrote:
What a lot of comments! This deserves a reply at length. I state a
lot
of things below as fact. But snce I'm still pretty ignorant about nfs4
some of them may not be true. Those who know please put in corrections;
and we may arrive at the truth about something that's still pretty murky
to most people. Comments on particular postings follow.
Nfs4 exports a tree of directories from a server to a client. The root
of the tree must be the root of the filesystem on the host and the
line containing it in /etc/exports must contain the option fsid=root
(alternately fsid=0). If such a line appears in /etc/exports then any
directory on the server can be exported, and the client can mount any
directory appearing there. Nfs4 works through a firewall, provided
that port port 2049/tcp is opened; nfs3 requires that the firewall be
(completely) disabled. "showmount -e <host>" doesn't work through
a
firewall, it appears to be associated with nfs3. There is no utility
like it that works through port 2049/tcp; administrators have to know
which files are available via the nfs4 port from which servers.
There's an intro to setting up nfs4 (link from Ed Greshko) that states
that the fsid=0 option can be applied to any directory, and then other
directories to be exported should be (bound to) subdirectories of this
one; but I haven't been able to get it to work. Funky problems:
1) If the client has an actual name or exact IP address in /etc/exports,
like this line:
/nfs4 amito:/(rw,fsid=0,...)
or
/nfs4 192.168.2.5(rw,fsid=0,...)
mount attempts fail with the message "No such file or directory".
2)If the line in /etc/exports has a form like
/nfs4 192.168.0.0/24(rw,fsid=0,...)
mount attempts fail with the message "access denied by server".
There's probably some problem with the options in the parentheses,
but I've tried them all, starting with the exact ones in the intro
without success. On the other hand, exporting the actual root
/ amito:(rw,fsid=0,..)
mounts fine.
I hope to be enlightened.
A few things....
First, it may be helpful for you to post the contents of your server's /etc/exports
and /etc/fstab.
Second, have you modified your idmap.conf such that you have identical Domain =
lines? Note that after modification the nfs-idmap.service needs to be restarted.
--
Never be afraid to laugh at yourself, after all, you could be missing out on the joke
of the century. -- Dame Edna Everage
4 a.m.
New subject: mount -t nfs4 fails, but mount -t nfs succeeds [SOLVED]
On 04/27/2012 04:10 PM, Ed Greshko wrote:
Second, have you modified your idmap.conf such that you have
identical Domain =
lines? Note that after modification the nfs-idmap.service needs to be restarted.
You need this on both F16 client and server. This changes in F17.
--
Never be afraid to laugh at yourself, after all, you could be missing out on the joke
of the century. -- Dame Edna Everage
4:18 a.m.
New subject: mount -t nfs4 fails, but mount -t nfs succeeds [SOLVED]
On Fri, 2012-04-27 at 17:00 +0800, Ed Greshko wrote:
On 04/27/2012 04:10 PM, Ed Greshko wrote:
> Second, have you modified your idmap.conf such that you have identical Domain =
> lines? Note that after modification the nfs-idmap.service needs to be restarted.
It looks like these lines should be identical in /etc/idmapd.conf
between server client. As I wrote in my last posting, there are
no such lines (not commented out) in either file.
Thanks - jon
4:14 a.m.
New subject: mount -t nfs4 fails, but mount -t nfs succeeds [SOLVED]
On Fri, 2012-04-27 at 16:10 +0800, Ed Greshko wrote:
First, it may be helpful for you to post the contents of your
server's /etc/exports
and /etc/fstab.
Here they are. /etc/exports is much chewed up by many experiments; this
is its latest incarnation. /etc/fstab follows.
$ more exports
/ amito(rw,fsid=root,no_root_squash)
# /home/jonrysh amito(rw,no_root_squash)
# /var amito(rw,no_root_squash)
# /nfs4exports 192.168.0.0/24(ro,root_squash,no_subtree_check,fsid=0)
# /nfs4exports
192.168.0.0/24(ro,fsid=root,insecure,no_subtree_check,no_root_squash)
# /nfs4exports/home
192.168.0.0/24(rw,nohide,insecure,no_subtree_check,no_root_squash)
# /nfs4exports/sbin
192.168.0.0/24(rw,nohide,insecure,no_subtree_check,no_root_squash)
# /nfs4exports
192.168.2.5(ro,fsid=root,insecure,no_subtree_check,no_root_squash)
# /nfs4exports/home
192.168.2.5(rw,nohide,insecure,no_subtree_check,no_root_squash)
# /nfs4exports/sbin
192.168.2.5(rw,nohide,insecure,no_subtree_check,no_root_squash)
$ more fstab
# /etc/fstab
# Created by anaconda on Fri Mar 30 11:08:48 2012
#
# Accessible filesystems, by reference, are maintained under '/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
#
UUID=2df88f7e-a779-401a-8e47-0c32d500b5af / ext4 defaults
1 1
UUID=d64559f2-2e25-4a96-a937-bbe06516ab2c /boot ext4 defaults
1 2
UUID=2d7ec72f-f9af-4ec8-aff0-03d07ef30b73 /var ext4 defaults
1 2
UUID=5fb1efb6-3e12-437f-a12e-b60cb622d001 swap swap defaults
0 0
Second, have you modified your idmap.conf such that you have
identical
Domain =
lines? Note that after modification the nfs-idmap.service needs to be
restarted.
You must mean /etc/idmapd.conf . This file is untouched on both client
and server. It has a single "Domain = ..." line, which is commented
out. I'm not sure what it should be identical to. The value of this
variable should be the local domain name, which is null.
$ dnsdomainname
$ hostname --fqdn
amito
Thanks - jon
4:37 a.m.
New subject: mount -t nfs4 fails, but mount -t nfs succeeds [SOLVED]
On 04/27/2012 05:14 PM, Jonathan Ryshpan wrote:
On Fri, 2012-04-27 at 16:10 +0800, Ed Greshko wrote:
> First, it may be helpful for you to post the contents of your
> server's /etc/exports
> and /etc/fstab.
Here they are. /etc/exports is much chewed up by many experiments; this
is its latest incarnation. /etc/fstab follows.
$ more exports
/ amito(rw,fsid=root,no_root_squash)
# /home/jonrysh amito(rw,no_root_squash)
# /var amito(rw,no_root_squash)
# /nfs4exports 192.168.0.0/24(ro,root_squash,no_subtree_check,fsid=0)
# /nfs4exports
192.168.0.0/24(ro,fsid=root,insecure,no_subtree_check,no_root_squash)
# /nfs4exports/home
192.168.0.0/24(rw,nohide,insecure,no_subtree_check,no_root_squash)
# /nfs4exports/sbin
192.168.0.0/24(rw,nohide,insecure,no_subtree_check,no_root_squash)
# /nfs4exports
192.168.2.5(ro,fsid=root,insecure,no_subtree_check,no_root_squash)
# /nfs4exports/home
192.168.2.5(rw,nohide,insecure,no_subtree_check,no_root_squash)
# /nfs4exports/sbin
192.168.2.5(rw,nohide,insecure,no_subtree_check,no_root_squash)
For comparison, here is the relevant portion of my exports file....
/nfs4exports
192.168.0.0/24(ro,sync,insecure,root_squash,no_subtree_check,fsid=0)
/nfs4exports/syntegra
192.168.0.0/24(rw,nohide,sync,insecure,root_squash,no_subtree_check)
/nfs4exports/myhome
192.168.0.0/24(rw,nohide,sync,insecure,root_squash,no_subtree_check)
$ more fstab
# /etc/fstab
# Created by anaconda on Fri Mar 30 11:08:48 2012
#
# Accessible filesystems, by reference, are maintained under '/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
#
UUID=2df88f7e-a779-401a-8e47-0c32d500b5af / ext4 defaults
1 1
UUID=d64559f2-2e25-4a96-a937-bbe06516ab2c /boot ext4 defaults
1 2
UUID=2d7ec72f-f9af-4ec8-aff0-03d07ef30b73 /var ext4 defaults
1 2
UUID=5fb1efb6-3e12-437f-a12e-b60cb622d001 swap swap defaults
0 0
Can we assume you've issued the "mount --bind " commands on your server? (a
df would
show it) These don't survive reboots. So, eventually you will need the appropriate
lines in your fstab. These are mine for reference.
/syntegra /nfs4exports/syntegra none rw,bind 0 0
/home/egreshko /nfs4exports/myhome none rw,bind 0 0
and the output of df shows in part...
/syntegra 80634688 58323932 18214756 77% /nfs4exports/syntegra
/home/egreshko 366919872 186333032 161964808 54% /nfs4exports/myhome
> Second, have you modified your idmap.conf such that you have identical
> Domain =
> lines? Note that after modification the nfs-idmap.service needs to be
> restarted.
You must mean /etc/idmapd.conf . This file is untouched on both client
and server. It has a single "Domain = ..." line, which is commented
out.
Well, this is mainly used for proper uid/gid mapping between client and server. They
don't have to be "real". They can be set to mydomain.com or maybe even
left
blank....can't recall.
But, you will need to enable nfs-idmap.service on F16 to have your uids/gids mapped.
Otherwise you'll run into read/write permission problems.
--
Never be afraid to laugh at yourself, after all, you could be missing out on the joke
of the century. -- Dame Edna Everage
3:17 p.m.
On 26.4.2012 22:45, Jonathan Ryshpan wrote:
Can anyone explain this? How can it be fixed? Do some services need
to
be started on the server?
The server is "weather". This log is from the client:
# mount -t nfs weather:/home/jonrysh /mnt/weather
# ls /mnt/weather
Desktop Documents Downloads Music Pictures Public Templates Videos
grub2
# umount /mnt/weather
# mount -t nfs4 weather:/home/jonrysh /mnt/weather
mount.nfs4: mounting weather:/home/jonrysh failed, reason given by server:
No such file or directory
#
Thanks in advance - jon
Could you post your /etc/exports from "weather"
as the exports syntax is
different for nfs3 and nfs4.
-vpk
3:23 p.m.
On 04/26/2012 02:45 PM, Jonathan Ryshpan wrote:
Can anyone explain this? How can it be fixed? Do some services need
to
be started on the server?
The server is "weather". This log is from the client:
# mount -t nfs weather:/home/jonrysh /mnt/weather
# ls /mnt/weather
Desktop Documents Downloads Music Pictures Public Templates Videos grub2
# umount /mnt/weather
# mount -t nfs4 weather:/home/jonrysh /mnt/weather
mount.nfs4: mounting weather:/home/jonrysh failed, reason given by server:
No such file or directory
#
Thanks in advance - jon
NFSv4 works very differently from previous versions. You should be able
to Google up plenty of documentation.
The key point is that you can't just switch between v3 and v4 without
reconfiguring things.
--
========================================================================
Ian Pilcher arequipeno(a)gmail.com
"If you're going to shift my paradigm ... at least buy me dinner first."
========================================================================
3:38 p.m.
On Thu, 26 Apr 2012, Ian Pilcher wrote:
On 04/26/2012 02:45 PM, Jonathan Ryshpan wrote:
> Can anyone explain this? How can it be fixed? Do some services need to
> be started on the server?
>
> The server is "weather". This log is from the client:
> # mount -t nfs weather:/home/jonrysh /mnt/weather
> # ls /mnt/weather
> Desktop Documents Downloads Music Pictures Public Templates Videos
grub2
> # umount /mnt/weather
> # mount -t nfs4 weather:/home/jonrysh /mnt/weather
> mount.nfs4: mounting weather:/home/jonrysh failed, reason given by server:
> No such file or directory
> #
> Thanks in advance - jon
NFSv4 works very differently from previous versions. You should be
able to Google up plenty of documentation.
The key point is that you can't just switch between v3 and v4
without reconfiguring things.
possibly off-topic but a long, long, *long* time ago, i wondered if
you could set up a network using *exclusively* NFSv4, and found it was
impossible -- at least one of the client programs required some
earlier version of NFS even if it wasn't being used.
any clarification on whether one can run a *purely* NFSv4 network?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
1:38 p.m.
Robert P. J. Day wrote:
On Thu, 26 Apr 2012, Ian Pilcher wrote:
> On 04/26/2012 02:45 PM, Jonathan Ryshpan wrote:
>> Can anyone explain this? How can it be fixed? Do some services need to
>> be started on the server?
>>
>> The server is "weather". This log is from the client:
>> # mount -t nfs weather:/home/jonrysh /mnt/weather
>> # ls /mnt/weather
>> Desktop Documents Downloads Music Pictures Public Templates
Videos grub2
>> # umount /mnt/weather
>> # mount -t nfs4 weather:/home/jonrysh /mnt/weather
>> mount.nfs4: mounting weather:/home/jonrysh failed, reason given by
server:
>> No such file or directory
>> #
>> Thanks in advance - jon
>
> NFSv4 works very differently from previous versions. You should be
> able to Google up plenty of documentation.
>
> The key point is that you can't just switch between v3 and v4
> without reconfiguring things.
possibly off-topic but a long, long, *long* time ago, i wondered if
you could set up a network using *exclusively* NFSv4, and found it was
impossible -- at least one of the client programs required some
earlier version of NFS even if it wasn't being used.
any clarification on whether one can run a *purely* NFSv4 network?
I see no reason why not. On all machines at one site nfs4 is used to provide
idmap capability. That's the only kind of mount used, and a long look with
wireshark shows all nfs packets were V4, so I empirically conclude it works.
You have to diddle the firewall to get nfs3 to work IIRC.
--
Bill Davidsen <davidsen(a)tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
3:41 p.m.
On 04/27/2012 03:45 AM, Jonathan Ryshpan wrote:
Can anyone explain this? How can it be fixed? Do some services need
to
be started on the server?
The server is "weather". This log is from the client:
# mount -t nfs weather:/home/jonrysh /mnt/weather
# ls /mnt/weather
Desktop Documents Downloads Music Pictures Public Templates Videos grub2
# umount /mnt/weather
# mount -t nfs4 weather:/home/jonrysh /mnt/weather
mount.nfs4: mounting weather:/home/jonrysh failed, reason given by server:
No such file or directory
#
Thanks in advance - jon
If you do a "modprobe nfs" the mount would work....
See this https://bugzilla.redhat.com/show_bug.cgi?id=806333
--
Never be afraid to laugh at yourself, after all, you could be missing out on the joke
of the century. -- Dame Edna Everage
7:32 p.m.
On 04/27/2012 04:41 AM, Ed Greshko wrote:
On 04/27/2012 03:45 AM, Jonathan Ryshpan wrote:
> Can anyone explain this? How can it be fixed? Do some services need to
> be started on the server?
>
> The server is "weather". This log is from the client:
> # mount -t nfs weather:/home/jonrysh /mnt/weather
> # ls /mnt/weather
> Desktop Documents Downloads Music Pictures Public Templates Videos
grub2
> # umount /mnt/weather
> # mount -t nfs4 weather:/home/jonrysh /mnt/weather
> mount.nfs4: mounting weather:/home/jonrysh failed, reason given by server:
> No such file or directory
> #
> Thanks in advance - jon
>
If you do a "modprobe nfs" the mount would work....
See this https://bugzilla.redhat.com/show_bug.cgi?id=806333
Opppssss...
Cut and Pasted reply into wrong message... What this should have said was....
When working with NFSv4 I sometimes consult this for reference....
http://www.crazysquirrel.com/computing/debian/servers/setting-up-nfs4.jspx
--
Never be afraid to laugh at yourself, after all, you could be missing out on the joke
of the century. -- Dame Edna Everage
3:58 p.m.
what version of Fedora you use? (nfs server / nfs client)
can you attach /etc/exports and /etc/syconfig/nfs files?
can you attach /etc/sysconfig/iptables?
All of these files are from nfs server side.
On 26 April 2012 21:45, Jonathan Ryshpan <jonrysh(a)pacbell.net> wrote:
Can anyone explain this? How can it be fixed? Do some services need
to
be started on the server?
The server is "weather". This log is from the client:
# mount -t nfs weather:/home/jonrysh /mnt/weather
# ls /mnt/weather
Desktop Documents Downloads Music Pictures Public Templates Videos grub2
# umount /mnt/weather
# mount -t nfs4 weather:/home/jonrysh /mnt/weather
mount.nfs4: mounting weather:/home/jonrysh failed, reason given by server:
No such file or directory
#
Thanks in advance - jon
--
users mailing list
users(a)lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
4382
days inactive
4383
days old
20 comments
10 participants
participants (10)
-
Bill Davidsen -
Ed Greshko -
Ian Pilcher -
Joe Zeff -
Jonathan Ryshpan -
Kernel Guardian -
Michael Cronenworth -
Robert P. J. Day -
Tim -
Veli-Pekka Kestilä