NFSv4 Shares stopped working

English Network/Internet
1

Hi there,

after I have moved to another house, I got a new router a Fritz!Box 7560. Now my NSFv4 share for my NAS doesn’t work any longer. Even worse the boot procedure is now taking 1 minute and 50 seconds longer, because it tries to open a certain device with a completely unintuitive name …

So I first deleted the corresponding nsf share entry in the Yast/NSF client, rebooted the system (still slow boot) and tried to add a new NSF entry … ‘Choose’ could find the NAS (static IP: 192.168.178.xxx), but whenever I click on ‘Select’ and ‘NSFv4 Share’ is checked, I get in the ‘exported directories’ window an ‘internal error’ instead of a shared volumes name …

So I tried the same procedure again, but leaving this time the ‘NSFv4 Share’ unchecked and I got a list of valid looking subdirectories, can select one and can finish the Add-procedure without any error message. But unfortunately these shares do not work … there is nothing at all in the subdirectory defined as ‘Mount Point’. But also no error message or warning or what so ever. Just putting everything under the carpet …

I meanwhile have solved the problem with the slow boot: In Yast/Partitioner I found an entry for the NAS with its IP number … by removing this entry I solved the problem with the slow boot. Just wondering how it was possible to create such a cryptic name for this device, so that one has no clue what could be meant.

I am now forced to use Samba to get access to the content of my NAS … but the use of a Samba drive seems to be very restricted - Amarok does not liek it and does not allow me to scan my music files on the NAS.

BTW. Both Windows 7 64 pro , the one in the Virtualbox and the stand-alone installation work in the new environment, I simply had to change to the new subnet (before 192.168.2.0/24, now 192.168.178.0/24) and it worked again.

The Fritz!Box is doing the DHCP, the DNS and is the Master for the Windows Workgroup.

The NAS is a Synology DS214 which is working since almost 2 years without a problem. The software is up to date.

Any ideas what could be wrong with the NSF client and it it had any complains, where I could find them ?

TIA, Joe

2

Hi there,

after the re-installation of my virtualbox (it suddenly stopped working today) my virtualbox worked again.

So I thought may be, may be there is a stupid connection between both and I tried again to create an NSFv4 shar; it did not work. Tried it without v4 and I could create it as known and it did still not work. So I removed that NSF share again.

But I had to find out, that it did not remove the entry in fstab (Yast/Partitioner) … slow boot and slow shut down again. That let’s me assume that there is something internal going wrong. Is there a log for NSF actions ?

TIA, Joe

3

Hi guys,

nobody here has an idea what could be wrong or what I could do to find out what’s wrong ? It’s still not working.

TIA,
Joe

4

As nobody seems to have a clue it must be a kind of super duper high technology problem.
Really nobody else with a similar problem ?

Joe

5

btw. the log at /var/log/messages mentioned in the partitioner … does not exist.

So where can I get more information ?

Is this related ? : https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1385846

TIA, Joe

6

BTW am NON-Technical, still…

Using File Type naming conventions may help.

Self with file stored on other computer sometimes file type not recognized when NOT copied across, but play from other computer.

After Samba copied file across, can listen/view them as audio/video files rarely with problem [linux examines actual file with less concern for naming conventions].

Linux dislikes “blank space” in file name which may cause similar problems, or file renaming.

(NFS may view distant folders as part local machine, still to learn how to set up and use NFS. )

.

7

I somehow missed this thread. A assume people did not start answering because you are telling a long, long story, but do not provide any technical information in your first post. E.g. you are talking about an /etc/fstab entry but it is nowhere to be seen. Thus comment on it being correct or not is impossible.

Now of course people can post and start pulling from you those bits and pieces (and I sometimes do it even in threads where I have no expertise because as a mod I try to get things on the move), but people are not always in the mood to get into, what then often becomes, a difficult discussion with a lot of mutual misunderstanding.

So maybe, when you try to offer a good factual description on what you have, accompanied by computer facts like exports definitions from the NFS server and fstab entries on the client). And what you expect to happen. And on what happens instead (including any messages you got/find). Then people could maybe make a start on attacking your problem.

8

Hi Henk,

thanks for your reply.

If I would have any technical support from the OS 42.1, i.e. log files or similar concerning that NSF problem, as I had it before with OS 13.1 & 13.2, I for sure would have started to find out what’s wrong and if if could not have found a solution, I would have published it here with a hopeful relevant part of the log file or other piece of information. But the only information OS 42.1 gave me was “Internal Error”, which is even shorter than M$ error messages usually are and the fact that NSF shares simply do not work any longer. So I can provide you, with a list of my hardware, a list of installed partitions, different virtual machines & software etc. in the hope hoping that I do not bore you too much … or give me a hint what would in this NSF case really be a valuable information and where can I find it.

If you or someone else could provide me with information how I could collect relevant further information (i.e. a location of a log file would be very much appreciated) , I would be very happy.

Thanks in advance for your answer,
Joe