Udo Grabowski wrote: > Opensolaris 2009.6 snv 111b BOTH client and server > We have a nested mirrormount NFSv4 over 1Gb/s tcp. Running only 30 jobs on a > single host > (X4600M2) via SGE intermittently (30% of all jobs, sometimes even more !) > gives Shepherd error: > > can't stat() "/home/Processor/xxx/yyy/zzz/..../aaa.log" as stdout_path: > Device busy KRB5CCAME=none .... > >
Most likely this is bug: http://bugs.opensolaris.org/view_bug.do?bug_id=6636260 > We've not seen this without mirrormounts. Could it be that there's a single > threaded bottleneck > which triggers this error (I've seen a similar problem with ramdiskadm, you > can't create more > than one ramdisk at a time with two parallel commands, it also gives 'device > busy'). ? > > No, not likely. > > We're trying to run NFSv4 for over a year now, and no OS version is able to > deliver without severe > problems (see,e.g.,my earlier post > <http://www.opensolaris.org/jive/thread.jspa?threadID=103920&tstart=45>, > "data corruption with NFS4/ZFS", that symptom is now worse with both > server and client on OSol). > Will NFSv4 be a sandbox for developers forever or is it planned to make it > usable for enterprise > production some day ? It ships on by default. NFSv4 is not a sandbox for developers and it used in enterprise production today. All of sun.com runs on NFSv4 and *not* NFSv3. I believe the phrase for such deployment is that "we eat our own dog food." And I have never heard anyone claim that we should go back to NFSv3 internally. > At least, there should be a statement in the release notes that NFSv4 is not > usable for production yet because of multiple issues. You can find multiple issues for NFSv3, does that make it not ready for production? I can find multiple issues for CIFS (on XP), Fallout 3, VMWare, etc. Does that mean that they are not ready for production? You can pick any piece of complex software and find issues with it. > Do we have again to go back to v3 and wait > until v5 will give better experience ? You'll want NFSv4.1 (and the resulting pNFS) when it ships. > Or is NFS development effectively dead in opensolaris because > Osol now concentrates on the "typical desktop user" who does not need NFS ? > NFS development has nothing to do with "typical desktop user". OpenSolaris means many things, you've chosen to focus on just one aspect. As NFS developers, our focus in the context of shipping OpenSolaris bits is in bug fixes. And in that regard, we don't focus on who our user is - instead we focus on security issues, quality, panics, and interoperability. In the context of non-shipping OpenSolaris bits, we focus on NFSv4.1 and pNFS. We maintain a development gate that we keep synced with the ON gate. We do not push changes from our nfs41 gate back to ON because we do not have a production ready system and we do not consider ON to be a sandbox. By the way, that was almost the exact same development model we used in delivering NFSv4 to Solaris 10. > No, we do not plan to step back to solaris 10 ("./configure; => Error: at > least version xxx of package yyy needed ..." => hopelessly outdated software > versions for our needs !), and we really need v4 > with mirrormount capability for our complex and dynamic directory layouts > (too much work on v3 to > keep up the automount tables, bad performance for ~300 clients). > Sorry for ranting, but I get really upset because any new release of SXDE, > Opensolaris or > whatever gives us another step back instead of forward. We are not developing > OSol, but we need to > work with it ! You should really concentrate on consolidating code instead of > incorporating more and > more new stuff which does not really work when it comes to real production. > There are so many > open bugs in this area. > So, the first question is whether or not you are paying for support with OpenSolaris? If so, you have other avenues to explore raising this issue. If not, then you should really consider why you expect enterprise quality code at no cost to yourself. Within the context of NFSv4, mirrormounts was the last feature development delivered to OpenSolaris. And that was on Oct 22nd, 2007. You can see the notice I sent out here: http://blogs.sun.com/tdh/entry/we_just_delivered_mirror_mounts The remaining work done to date for NFSv4 in OpenSolaris has been bug fixes. BTW - please be clear, I'm not claiming that further NFSv4 based feature work will not appear in OpenSolaris, but I am claiming that you've had almost 2 years of feature free additions.
