NFS was working until i rebooted the client machine. I was going to hook
up some hardware and forgot. Now i am having a hard time finding the
configuration files. The client machine (oS 11.1, KDE 3.5) is supposed to
use automount to connect, but i can’t seem to find the configuration files
and yast does not help. Same issue with the server (os 11.3, KDE 3.5). If
i could find the configuration files, else i would have included them in
code blocks.
Any Helpers?
?-)
BTW am NON-Technical !
HELP : open terminal view then type: man nfs
HELP : open link in browser: openSUSE 12.3: Chapter 18. Sharing File Systems with NFS
Under heading Description in the man nfs it tells how “…NFS file system mounts, a line in the /etc/fstab file specifies…”
As also trying to figure NFS out, shall leave better advice to those who do understand NFS 
.
josephkk wrote:
> NFS was working until i rebooted the client machine. I was going to hook
> up some hardware and forgot. Now i am having a hard time finding the
> configuration files. The client machine (oS 11.1, KDE 3.5) is supposed to
> use automount to connect, but i can’t seem to find the configuration files
> and yast does not help. Same issue with the server (os 11.3, KDE 3.5). If
> i could find the configuration files, else i would have included them in
> code blocks.
Can you explain what you mean by “yast does not help”. It works well for
most people, so you’ll need to tell us explicitly what doesn’t work for you.
As regards config, the first place to look on the client is /etc/fstab
and the first place on the server is /etc/exports
You should also look in /var/log/messages on both machines and tell us
what you see that’s related to NFS.
And try mount -v <name-of-filesystem> on the client and tell us what it
says.
On Mon, 08 Apr 2013 10:16:19 GMT, Dave Howorth
<djh-novell@no-mx.forums.opensuse.org> wrote:
>josephkk wrote:
>> NFS was working until i rebooted the client machine. I was going to hook
>> up some hardware and forgot. Now i am having a hard time finding the
>> configuration files. The client machine (oS 11.1, KDE 3.5) is supposed to
>> use automount to connect, but i can’t seem to find the configuration files
>> and yast does not help. Same issue with the server (os 11.3, KDE 3.5). If
>> i could find the configuration files, else i would have included them in
>> code blocks.
>
>Can you explain what you mean by “yast does not help”. It works well for
>most people, so you’ll need to tell us explicitly what doesn’t work for you.
Using Yast to setup the client does not yield a working NFS mount.
Using Yast to setup the server does not yield a usable NFS service.
>
>and the first place on the server is /etc/exports
>As regards config, the first place to look on the client is /etc/fstab
I thought i said i am using automount. Where are those config files?
joseph2k@Dumbarton:~> cat /etc/fstab
/dev/disk/by-id/ata-IC35L120AVV207-1_VNVD05G4CUGRUT-part5 swap swap
defaults 0 0
/dev/disk/by-id/ata-WDC_WD1600AAJB-00J3A0_WD-WCAV3E506390-part7 / ext3
acl,user_xattr 1 1
/dev/disk/by-id/ata-WDC_WD1600AAJB-00J3A0_WD-WCAV3E506390-part8 /home ext3
acl,user_xattr 1 2
/dev/disk/by-id/ata-WDC_WD1600AAJB-00J3A0_WD-WCAV3E506390-part1 /windows/C
ntfs-3g users,gid=users,fmask=133,dmask=022,locale=en_US.UTF-8 0 0
/dev/disk/by-id/ata-WDC_WD1600AAJB-00J3A0_WD-WCAV3E506390-part5 /windows/D
vfat users,gid=users,umask=0002,utf8=true 0 0
/dev/disk/by-id/ata-WDC_WD1600AAJB-00J3A0_WD-WCAV3E506390-part6 /windows/E
vfat users,gid=users,umask=0002,utf8=true 0 0
/dev/disk/by-id/ata-IC35L120AVV207-1_VNVD05G4CUGRUT-part6 /windows/F
vfat users,gid=users,umask=0002,utf8=true 0 0
proc /proc proc defaults 0 0
sysfs /sys sysfs noauto 0 0
debugfs /sys/kernel/debug debugfs noauto 0 0
usbfs /proc/bus/usb usbfs noauto 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0
nas-F4:/c/Joseph2k /media/Joseph-nas-F4 nfs
rw,sync,hard,intr,user=2000,users,exec,suid 0 0
Godel:/media/disk-2 /media/Eagledisk nfs
rw,sync,hard,intr,exec,dev,suid 0 0
LABEL=Oldsuse9.2 /media/BulkStore2 ext3
noatime,user,noacl,user_xattr 1 2
LABEL=Massvol3 /media/Massvol3 ext3 defaults 1 2
LABEL=WDC-Repl-V1 /media/WDC-Repl-V1 ext3 defaults 1 2
joseph2k@Dumbarton:~>
>
>You should also look in /var/log/messages on both machines and tell us
>what you see that’s related to NFS.
>
>And try mount -v <name-of-filesystem> on the client and tell us what it
>says.
Does this provide information that you can understand to guide me?
?-)
josephkk wrote:
> On Mon, 08 Apr 2013 10:16:19 GMT, Dave Howorth
> <djh-novell@no-mx.forums.opensuse.org> wrote:
>
>> josephkk wrote:
>>> NFS was working until i rebooted the client machine. I was going to hook
>>> up some hardware and forgot. Now i am having a hard time finding the
>>> configuration files. The client machine (oS 11.1, KDE 3.5) is supposed to
>>> use automount to connect, but i can’t seem to find the configuration files
>>> and yast does not help. Same issue with the server (os 11.3, KDE 3.5). If
>>> i could find the configuration files, else i would have included them in
>>> code blocks.
>> Can you explain what you mean by “yast does not help”. It works well for
>> most people, so you’ll need to tell us explicitly what doesn’t work for you.
>
> Using Yast to setup the client does not yield a working NFS mount.
> Using Yast to setup the server does not yield a usable NFS service.
Well, thanks for the really helpful description of the problem, NOT 
>> and the first place on the server is /etc/exports
>
> CODE:
> ---------------------------
> Godel:~ # cat /etc/exports
> /media/disk-2 192.168.1.*(rw,root_squash,sync,hard,no_subtree_check)
> Godel:~ #
> ---------------------------
>
>> As regards config, the first place to look on the client is /etc/fstab
>
> I thought i said i am using automount. Where are those config files?
I have no idea.
> CODE: <blank lines inserted because my news client cannot easily be made
> to not wrap>
Get a better news client or post using the web?
> --------------------------
> joseph2k@Dumbarton:~> cat /etc/fstab
> /dev/disk/by-id/ata-IC35L120AVV207-1_VNVD05G4CUGRUT-part5 swap swap
> defaults 0 0
>
> /dev/disk/by-id/ata-WDC_WD1600AAJB-00J3A0_WD-WCAV3E506390-part7 / ext3
> acl,user_xattr 1 1
>
> /dev/disk/by-id/ata-WDC_WD1600AAJB-00J3A0_WD-WCAV3E506390-part8 /home ext3
> acl,user_xattr 1 2
>
> /dev/disk/by-id/ata-WDC_WD1600AAJB-00J3A0_WD-WCAV3E506390-part1 /windows/C
> ntfs-3g users,gid=users,fmask=133,dmask=022,locale=en_US.UTF-8 0 0
>
> /dev/disk/by-id/ata-WDC_WD1600AAJB-00J3A0_WD-WCAV3E506390-part5 /windows/D
> vfat users,gid=users,umask=0002,utf8=true 0 0
>
> /dev/disk/by-id/ata-WDC_WD1600AAJB-00J3A0_WD-WCAV3E506390-part6 /windows/E
> vfat users,gid=users,umask=0002,utf8=true 0 0
>
> /dev/disk/by-id/ata-IC35L120AVV207-1_VNVD05G4CUGRUT-part6 /windows/F
> vfat users,gid=users,umask=0002,utf8=true 0 0
>
> proc /proc proc defaults 0 0
>
> sysfs /sys sysfs noauto 0 0
>
> debugfs /sys/kernel/debug debugfs noauto 0 0
>
> usbfs /proc/bus/usb usbfs noauto 0 0
>
> devpts /dev/pts devpts mode=0620,gid=5 0 0
>
> * nas-F4:/c/Joseph2k /media/Joseph-nas-F4 nfs
> rw,sync,hard,intr,user=2000,users,exec,suid 0 0
>
> * Godel:/media/disk-2 /media/Eagledisk nfs
> rw,sync,hard,intr,exec,dev,suid 0 0
>
> LABEL=Oldsuse9.2 /media/BulkStore2 ext3
> noatime,user,noacl,user_xattr 1 2
>
> LABEL=Massvol3 /media/Massvol3 ext3 defaults 1 2
>
> LABEL=WDC-Repl-V1 /media/WDC-Repl-V1 ext3 defaults 1 2
>
> joseph2k@Dumbarton:~>
>
> --------------------------
>> You should also look in /var/log/messages on both machines and tell us
>> what you see that’s related to NFS.
>>
>> And try mount -v <name-of-filesystem> on the client and tell us what it
>> says.
>
>
> CODE:
> ---------------------------
> Dumbarton:~ # mount -v -t nfs -o rw,sync,hard,intr,exec
> Godel:/media/disk-2 /media/Eagledisk/
> mount.nfs: timeout set for Tue Apr 9 18:43:50 2013
> mount.nfs: text-based options: ‘hard,intr,addr=192.168.1.101’
> mount.nfs: trying 192.168.1.101 prog 100003 vers 3 prot TCP port 2049
> mount.nfs: trying 192.168.1.101 prog 100005 vers 3 prot UDP port 36514
> mount.nfs: text-based options (retry):
> ‘hard,intr,addr=192.168.1.101,nfsvers=3,proto=tcp,mountproto=udp’
> mount.nfs: mount(2): Input/output error
> mount.nfs: mount system call failed
> Dumbarton:~ #
> ---------------------------
>
> Does this provide information that you can understand to guide me?
Where are the logs, especially from the server, at the time you made
this mount?
> ?-)
On Wed, 10 Apr 2013 10:07:28 GMT, Dave Howorth
<djh-novell@no-mx.forums.opensuse.org> wrote:
>josephkk wrote:
>> On Mon, 08 Apr 2013 10:16:19 GMT, Dave Howorth
>> <djh-novell@no-mx.forums.opensuse.org> wrote:
>>
>>> josephkk wrote:
>>>> NFS was working until i rebooted the client machine. I was going tohook
>>>> up some hardware and forgot. Now i am having a hard time finding the
>>>> configuration files. The client machine (oS 11.1, KDE 3.5) is supposed to
>>>> use automount to connect, but i can’t seem to find the configurationfiles
>>>> and yast does not help. Same issue with the server (os 11.3, KDE 3.5). If
>>>> i could find the configuration files, else i would have included them in
>>>> code blocks.
>>> Can you explain what you mean by “yast does not help”. It works well for
>>> most people, so you’ll need to tell us explicitly what doesn’t work for you.
>>
>> Using Yast to setup the client does not yield a working NFS mount.
>> Using Yast to setup the server does not yield a usable NFS service.
>
>Well, thanks for the really helpful description of the problem, NOT
I have been fighting this for weeks, and did not log everything i did.
Though it all was on the client machine.
>
>>> and the first place on the server is /etc/exports
>>
>> CODE:
>> ---------------------------
>> Godel:~ # cat /etc/exports
>> /media/disk-2 192.168.1.*(rw,root_squash,sync,hard,no_subtree_check)
>> Godel:~ #
>> ---------------------------
>>
>>> As regards config, the first place to look on the client is /etc/fstab
>>
>> I thought i said i am using automount. Where are those config files?
>
>I have no idea.
>
>> CODE: <blank lines inserted because my news client cannot easily be made
>> to not wrap>
>
>Get a better news client or post using the web?
>
>> --------------------------
>> joseph2k@Dumbarton:~> cat /etc/fstab
>> /dev/disk/by-id/ata-IC35L120AVV207-1_VNVD05G4CUGRUT-part5 swap swap
>> defaults 0 0
>>
>> /dev/disk/by-id/ata-WDC_WD1600AAJB-00J3A0_WD-WCAV3E506390-part7 / ext3
>> acl,user_xattr 1 1
>>
>> /dev/disk/by-id/ata-WDC_WD1600AAJB-00J3A0_WD-WCAV3E506390-part8 /home ext3
>> acl,user_xattr 1 2
>>
>> /dev/disk/by-id/ata-WDC_WD1600AAJB-00J3A0_WD-WCAV3E506390-part1 /windows/C
>> ntfs-3g users,gid=users,fmask=133,dmask=022,locale=en_US.UTF-80 0
>>
>> /dev/disk/by-id/ata-WDC_WD1600AAJB-00J3A0_WD-WCAV3E506390-part5 /windows/D
>> vfat users,gid=users,umask=0002,utf8=true 0 0
>>
>> /dev/disk/by-id/ata-WDC_WD1600AAJB-00J3A0_WD-WCAV3E506390-part6 /windows/E
>> vfat users,gid=users,umask=0002,utf8=true 0 0
>>
>> /dev/disk/by-id/ata-IC35L120AVV207-1_VNVD05G4CUGRUT-part6 /windows/F
>> vfat users,gid=users,umask=0002,utf8=true 0 0
>>
>> proc /proc proc defaults 0 0
>>
>> sysfs /sys sysfs noauto 0 0
>>
>> debugfs /sys/kernel/debug debugfs noauto 0 0
>>
>> usbfs /proc/bus/usb usbfs noauto 0 0
>>
>> devpts /dev/pts devpts mode=0620,gid=5 0 0
>>
>> * nas-F4:/c/Joseph2k /media/Joseph-nas-F4 nfs
>> rw,sync,hard,intr,user=2000,users,exec,suid 0 0
>>
>> * Godel:/media/disk-2 /media/Eagledisk nfs
>> rw,sync,hard,intr,exec,dev,suid 0 0
>>
>> LABEL=Oldsuse9.2 /media/BulkStore2 ext3
>> noatime,user,noacl,user_xattr 1 2
>>
>> LABEL=Massvol3 /media/Massvol3 ext3 defaults 1 2
>>
>> LABEL=WDC-Repl-V1 /media/WDC-Repl-V1 ext3 defaults 1 2
>>
>> joseph2k@Dumbarton:~>
>>
>> --------------------------
>>> You should also look in /var/log/messages on both machines and tell us
>>> what you see that’s related to NFS.
>>>
>>> And try mount -v <name-of-filesystem> on the client and tell us what it
>>> says.
>>
>>
>> CODE:
>> ---------------------------
>> Dumbarton:~ # mount -v -t nfs -o rw,sync,hard,intr,exec
>> Godel:/media/disk-2 /media/Eagledisk/
>> mount.nfs: timeout set for Tue Apr 9 18:43:50 2013
>> mount.nfs: text-based options: ‘hard,intr,addr=192.168.1.101’
>> mount.nfs: trying 192.168.1.101 prog 100003 vers 3 prot TCP port 2049
>> mount.nfs: trying 192.168.1.101 prog 100005 vers 3 prot UDP port 36514
>> mount.nfs: text-based options (retry):
>> ‘hard,intr,addr=192.168.1.101,nfsvers=3,proto=tcp,mountproto=udp’
>> mount.nfs: mount(2): Input/output error
>> mount.nfs: mount system call failed
>> Dumbarton:~ #
>> ---------------------------
>>
>> Does this provide information that you can understand to guide me?
>
>Where are the logs, especially from the server, at the time you made
>this mount?
>
Does this help?
>> ?-)
The NFS and Services start modules within YAST OS12.3 are both very buggy. This has to do with the switch to Systemd the new init system in 12.3.
allianux wrote:
> The NFS and Services start modules within YAST OS12.3 are both very
> buggy. This has to do with the switch to Systemd the new init system in
> 12.3.
If you read the OP’s first post, you’ll see that 12.3 is not relevant.
josephkk wrote:
> Does this help?
Difficult to know. It’s not what I asked you for and you’ve proven such
hard work to talk to that I’m out of here. But who knows, maybe somebody
else will come along and want to help.
On 04/06/2013 05:14 AM, josephkk wrote:
>
> . . . client machine (oS 11.1, KDE 3.5) . . .
> . . . the server (os 11.3, KDE 3.5) . . .
>
> Any Helpers?
here is the best help i can give: since openSUSE 11.3 met its
end-of-life on January 20th 2012 (cite
http://en.opensuse.org/Lifetime) and therefor have
received neither security patches nor bug fixes you should
immediately remove those two systems from any network exposed to
potential crackers, and then upgrade both at your leisure (but as
soon as possible) to a supported version!
you might upgrade to either 12.2 or 12.3, or if i were doing it i’d
first upgrade to 11.4 and then apply Evergreen to that…that would
leave you with a system supported until July 2014 (longer than 12.2
and just two months short of the 12.3 end-of-life) AND it would be a
system very familiar to you (whereas, both of the 12.x series are
relatively different)
here is the easy way (add one repo and then run YaST Online Update)
to adding Evergreen to openSUSE 11.4: http://tinyurl.com/4aflkpy
to first upgrade from 11.3 to 11.4, choose one of these paths and
follow the step-by-step carefully:
http://tinyurl.com/35p966c
http://tinyurl.com/93uemsr
http://tinyurl.com/7l4m2td
note: any of those paths might not result in a successful upgrade
but, mixing steps from one path with those of another path is even
less likely to result in a smile…so, backup first, pick ONE path
and follow it . . .
On Fri, 12 Apr 2013 14:22:46 GMT, Dave Howorth
<djh-novell@no-mx.forums.opensuse.org> wrote:
>josephkk wrote:
>> Does this help?
>
>Difficult to know. It’s not what I asked you for and you’ve proven such
>hard work to talk to that I’m out of here. But who knows, maybe somebody
>else will come along and want to help.
Well at least you tried. Sorry i couldn"t give you the information you
were expecting. Oh well.
?-)
Any other takers on NFS problems?
??:-?
On 2013-04-10 04:00, josephkk wrote:
> <blank lines inserted because my news client cannot easily be made
> to not wrap>
I see you use “Forte Agent”.
With Thunderbird there is a similar problem, but if you paste the text
with “paste as quotation” it does not wrap. True, there is a “>” on each
line, but at least the wrapping is correct.
> ....long line ...............................................................................................
As to your problem with NFS, you are using obsolete openSUSE versions at
both ends, so I can not really help. I can not try to emulate a similar
configuration, for instance.
And you have basic errors:
Godel:~ # cat /etc/exports
/media/disk-2 192.168.1.*(rw,root_squash,sync,hard,no_subtree_check)
Godel:~ #
You can not export from /media, that’s a temporary mount directory
reserved for the system. The filesystem may be there at the time that
nfsserver starts or not.
Regarding automount, that’s not something I’m familiar - and I can not
look up the documentation for such an obsolete system.
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
On 04/17/2013 05:03 AM, Carlos E. R. wrote:
>
> paste the text with “paste as quotation” it does not wrap.
THANKS! (i didn’t know that)
and, on the obsolete versions problem: +1
–
dd
On 2013-04-17 07:50, dd wrote:
> On 04/17/2013 05:03 AM, Carlos E. R. wrote:
>
>>
>> paste the text with “paste as quotation” it does not wrap.
>
> THANKS! (i didn’t know that)
Welcome. When posting in html mode, one of the available paragraphs
types does not wrap. This possibility is, sadly, not available when we
use plain text mode; it would be useful.
The workaround is the one above…
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
josephkk wrote:
>
> NFS was working until i rebooted the client machine. I was going to hook
> up some hardware and forgot. Now i am having a hard time finding the
> configuration files. The client machine (oS 11.1, KDE 3.5) is supposed to
> use automount to connect, but i can’t seem to find the configuration files
> and yast does not help. Same issue with the server (os 11.3, KDE 3.5). If
> i could find the configuration files, else i would have included them in
> code blocks.
>
> Any Helpers?
>
> ?-)
Sorry you haven’t been getting your system up and running.
If it’s not too late, some reminders.
(I’m using NDDLC as the server)
In /etc, create both auto.master like this (remember to do it as root)
/mnt/NDDLC /etc/auto.NDDLC --timeout=100
+auto.master
Then, auto.NDDLC like this
NDDLCDesktop -intr,nosuid 192.168.0.150:/home/rsmits/Documents
You will need to substitute the appropriate locations in your file, of
course.
Next export your files from the server - you can use yast then nfsserver,
which isn’t installed by default.
system, system services runlevel and be sure autofs is enabled, and nfs
services.
I think that’s all you need to do.
Once you have it working, burn a copy of the necessary files to a backup
somewhere for next time.
OpenSuse