I am still unable to find any solutions to Connecting my Client to NFS Server shares…
If someone solved this issue please post solution link !
Thanks All,
Mav
On 11/09/2012 08:26 AM, MavGuardian wrote:
>
> please post solution link !
http://is.gd/2BfI3 and don’t overlook the next section down, beginning
with “Before . . .”
–
dd
OpenSUSE 12.1 vs OpenSUSE 12.2 ]
I believe the current solution is to down-grade to 12.1 because 12.2 is not really production ready !
the only PC that couldn’t connect to nfs shares was the 12.2 PC…
Thanks guys
On 11/10/2012 09:06 PM, MavGuardian wrote:
> not really production ready
and so you logged the bug you found against 12.2 and your system with
bugzilla: http://tinyurl.com/nzhq7j
that way 12.2 can be fixed and 12.3 will be born without this bug…
the users are the final testers–unreported bugs almost never get fixed.
–
dd
Reply to the title: no waiting at all, it works fine. Just tested by connecting to two NFS shares, one from my 11.4 servermachine, one from another PC in the house running 12.2
There is no solution to a problem that IMHO does not exist. Please post output of
Server side
cat /etc/exports
Client side
cat /etc/fstab
To be honest with you all, one of the reasons I left Fedora is because I’m not Crash Dummy!
I just want an Operating System that WORKS so I can get back to my own work.
I don’t have time to test betas and I find it really abusive for anyone to not tell you up front “you’re a Crash Dummy” as Fedora doesn’t !
in certain circles they are open about it, but to the general public, unless you read EVERYTHING they write, it is portrayed as the community version of RedHat,
I am VERY thankfully deeply appreciate people who have time to test and be betas users for open source software like this, but that’s why I donate money every year!
Sorry I don’t have time for testing OS’s : )
Thanks for understanding, I just want things to work, so I can !
Regards All,
Mav (Applications Developer)
PS: I downgraded server and PC to 12.1 so I can’t get outputs, and since they are on 12.1, all is as it should be, Stable!
MavGuardian wrote:
> I am VERY thankfully deeply appreciate people who have time to test and
> be betas users for open source software like this, but that’s why I
> donate money every year!
> Sorry I don’t have time for testing OS’s : )
Sounds like you would be better off with SLES/SLED
I posted a ‘hack’ in several occasions, including in this thread http://forums.opensuse.org/english/get-technical-help-here/install-boot-login/479505-rpcbind-still-starts-late-systemd.html, which doesn’t seem to have received much attention.
If you google a little bit, you might find a better solution, consisting of writing a dedicated systemd service, which requires rpcbind to be running before mounting NFS shares. I haven’t tried (no time).
On 11/12/2012 09:06 PM, MavGuardian wrote:
> I just want things to work
i hear SUSE Linux Enterprise Desktop (SLED) is perfect…
i hear SUSE Linux Enterprise Server (SLES) is perfect…
i hear Macs are perfect…
i hear Red Hat Enterprise Linux is perfect…
i hear CentOS is perfect…
i hear Debian is perfect…
i hear Microsoft is not perfect…
i hear openSUSE, Fedora, Ubuntu and a LOT of others fit the needs of
some, but not all, folks…personally, i’ve used nothing but Linux since
2002 and what i’m using now (openSUSE 11.4 Evergreen) is perfect for
me, otherwise i would use something else…
and i’d suggest you use what is perfect for you…
–
dd
I’m ok with being a crash test dummy, but I cannot get OpenSuse 12.2 to consistently connect via NFS between two OpenSuse 12.2 machines. The whole thing seems totally random and buggy, with bad default suggestions for server configurations and a really unintuitive protocol underneath. It’s the first time I’ve tried to implement NFS so I don’t know what is a bug and what is simply me not understanding what is supposed to happen. I’ve read about 10 FAQs and still am unenlightened and simply am going to stick with Samba for now (which doesn’t allow me to play videos in VLC across the network). Maybe someone can tell me what is a bug and what is me?
-
Are all of the shares supposed to show up as either a root (/) or /home, no matter what?
-
What is the cause of “internal error” when you click the select remote directory button to on the client NFS/add dialog box? Most of the time it is “internal error” and sometimes it is the root and home directories? Is that right?
+If you don’t click NFSv4 on both sides, does it just not work in OpenSuse 12.2?
- Having fsid=0 as a default option on the server side seems to cause some of the “internal errors”. I haven’t understood any of the explanations of what that is or why it is a default option. It seemed to work most often (at least marginally) when the server options were sync and rw and maybe bind=, with the other default suggestions deleted …
+On the client side, half the time when I had the fsid=0 and I would try to “select” a remote directory, YAST just hangs with a sub-dialog box trying to open, and the process needs to be terminated, or even killed.
-
On the server side, if you delete the host/wildcard, and then add a new one, the default options don’t appear (they are blank) until you try to type something, and then they all just flash into the screen - that has to be a small bug.
-
On the rare occasions when I could get the share to work, merely restarting the NFS client process caused it to stop working and afterward it would not go back to the way it was before.
-
On the server side, what is the bind= setting? It seems to be important – because it gets displayed as ‘bindmount’ – and maybe it even to helps, but since nothing ever was available to the client as anything other than root or home, I couldn’t figure out what that should do.
+Is there some kind of lag between when a working NFS folder is shared and when it is available? Seems like there may be a really long one, but I couldn’t tell, because usually it just didn’t work.
+I tried using the timeo= option and inter= and disabling firewalls, etc.; that made it so the client could confirm through the “choose” NFS Server Hostname dialog that I was talking about an NFS server … but otherwise didn’t help much with the long client-side lags.
- When I finally ditched NFS, on the server side I just said “stop” the service through the NFS screens, which seemed to skip something important, like deleting the share configuration … and when I was done, the folder that I had been trying to NFS-share was still displayed through dolphin as being shared (with that little blue globe icon) and then rendered into a symlink for the bindmount target! When I deleted the NFS configuration file after changing the bindmount target into the same as the folder name (ie, /home/folder1 bind=/home/folder1), that folder remained a symlink for the whole home partition on the machine (I couldn’t see what was in the folder, it just passed me back to the home folder). After spinning my wheels on that for a while, I restarted the whole machine and it went back to normal (the folder was a folder and not a synlink) and I was relieved and finally gave up.
I’ll be happy to file bug reports on this, but it is just such a confusing mess I seems better to bring it here first.
On 11/16/2012 02:26 PM, dtillberg wrote:
>
> I’ve read about 10 FAQs and still am unenlightened and simply
> am going to stick with Samba
it is easy to get conflicting info if you search the internet…suggest
you always stick to openSUSE sources, for openSUSE problems…easy to
do that with google’s site specifier, like did nothing from here help:
http://doc.opensuse.org/documentation/html/openSUSE/opensuse-reference/cha.nfs.html
and there might be other useful resources here:
in our docs
https://www.google.com/search?q=site:doc.opensuse.org+NFS (where the
above specific chapter 18 from the official documentation is number one hit)
in our wiki
https://www.google.com/search?q=site:en.opensuse.org+NFS (where
http://en.opensuse.org/SDB:Network_file_system is the number one hit)
in our forums
https://www.google.com/search?q=site:forums.opensuse.org+NFS (where
hundreds and hundreds of set up problems are found, and most solved)
Been done already, multiple times…
that way 12.2 can be fixed and 12.3 will be born without this bug…
It’s fixed in the 12.3 Milestone 1. Whatever they hell they did to fix it NEEDS to be pushed back to 12.2, but the developers obviously don’t care.
Systemd also needs to be optional, defaulting to not installed, until it’s fully developed and working. Who installs a non-working unfinished product full of bugs in a production environment as default? It’s as bad a the Aakonadi fiasco that’s been ongoing in KDE since 4.0 was released.
I totally agree “that’s so fedora” : )
Thanks !
AFAIK you can still use sysvinit-init, it’s in the repos.
To be honest, I don’t think it’s the client. On my laptop, which connects through WiFi, the NFS client works fine. Must say though, my server which runs NFS-server is still on 11.4
On 2012-11-18 23:56, suseconvert wrote:
> It’s fixed in the 12.3 Milestone 1. Whatever they hell they did to fix
> it NEEDS to be pushed back to 12.2, but the developers obviously don’t
> care.
>
> Systemd also needs to be optional, defaulting to not installed, until
> it’s fully developed and working. Who installs a non-working unfinished
> product full of bugs in a production environment as default? It’s as
> bad a the Aakonadi fiasco that’s been ongoing in KDE since 4.0 was
> released.
Not going to happen.
You can still boot with systemv, but systemv is totally going out of the
picture sooner or later.
Many see openSUSE as the place where stuff is tested for SLES, so we
have to suffer these problems in exchange for having it free.
So, we may see systemd usable in openSUSE as soon as, or after, SLES
ships with it. Today I read that the plans are to introduce systemd in
SLES 12.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” (Minas Tirith))
Which would in the near future leave you with a no longer supported sysvinit. IMPOV it’s a new thing that I haven’t found my way around with, but will manage to understand in time.
Sysvinit is working fine and should be supported until such time as it’s no longer needed. Right now, it’s needed on 12.2 mainly due to the NFS on boot issue with systemd. That seems to be fixed with 12.3 (and I stand by my opinion that the developers need to push that back to 12.2), so if that were the only issue with systemd NOW they can do away with sysvinit. It should’ve been optional in 12.2, or at the very least a fix to the NFS fiasco released as soon as it was discovered. However, they seem to be ignoring it and the cries from their users.
IMPOV it’s a new thing that I haven’t found my way around with, but will manage to understand in time.
My thoughts exactly. I actually look forward to progress, and have no problems with systemd replacing sysvinit, but not before it’s ready. It was not ready in 12.2, and 12.2 was my introduction to openSUSE. This issue almost made me turn back to Kubuntu. I understand bugs get though, but there is no excuse for ignoring something this serious. I really find it hard to believe it made it through the milestones and betas undiscovered. if I powered down my desktop everyday instead of suspending it, I most likely would have moved on. As it is, my media center was moved back to Kubuntu because it’s totally useless without NFS, and the rare times it is power cycled, I don’t want to have to remote into it to get it running properly again.
I am enjoying openSUSE and think the developers are doing a marvelous job. I just don’t think 12.2 is production quality. I will stick with it however. Perhaps 12.3 will be where I switch all my systemsd over to oS.
In fact you’re all hitting my reason to have my private policy to wait for at least three months before I bring servers to the latest version. I can tell you the bug does not exist for 12.2 clients -> 12.1 server or 11.4 server. A new customer has a server still running 11.3 (perfectly by the way, and on a well protected LAN) and wants 12.2 on it. The clients all (just 8) run 12.2 which he installed himself and suggested to install 12.1 first, wait a couple of months, then move to 12.2
I can hardly imagine the fix for the bug is not going to be pushed to 12.2, things like NFS are " so basic linux ", they should work flawlessly, I completely agree to that.
On 11/21/2012 03:26 PM, Knurpht wrote:
>
> In fact you’re all hitting my reason to have my private policy to wait
> for at least three months before I bring servers to the latest version.
> I can tell you the bug does not exist for 12.2 clients -> 12.1 server or
> 11.4 server. A new customer has a server still running 11.3 (perfectly
> by the way, and on a well protected LAN) and wants 12.2 on it. The
> clients all (just 8) run 12.2 which he installed himself and suggested
> to install 12.1 first, wait a couple of months, then move to 12.2
> I can hardly imagine the fix for the bug is not going to be pushed to
> 12.2, things like NFS are " so basic linux ", they should work
> flawlessly, I completely agree to that.
>
>
Just my opinion by systemd is nothing like systemd was yesterday… and
tomorrow, systemd will be nothing like systemd today… and I don’t see that
changing for at least another year… maybe more. Project stinks of massive
scope creep and a gazillion assumptions (and really bizarre project mgmt that
removes compatibility at a drop of a (red)hat). Systemd will cause more
problems than what it was trying to solve (what was it trying to solve anyhow?).
I do encourage everyone to follow the systemd devel mail list… it’s scary.
Also keep abreast of the udev changes the systemd folks are making and the fork
of udev made by the gentoo folks… and the comments from Linus…
Will systemd ever settle down… oh… sure… I suppose… but rocky road for the
next (at least) couple of years.
(feel free to flame me… but only if you’ve been monitoring what they’ve been
doing please…)
I think you are right, as a developer myself I can tell you that massive changes are being made and in all kinds of stable areas that had no problems at all before.
…and now simple rock solid things like NFS don’t work anymore,
I am yet to get it running after 10 years working with Linux and 2 months of trying and reading all kinds of posts telling me things are not right…
Linux is being systematically killed destroying the foundations of it’s stability with illusions of grander from someone that has no concept of perfection over profit.
The basis of freedom and what makes Linux so powerful !
TC
To get back to topic, anyone have any other ideas how I can get OpenSUSE Client to connect to NFS shares on a server ?
Thanks