mosemann@hoss.unl.edu (Russell Mosemann) (08/16/90)
Two months ago, I installed CAP+ and UAB+ on a SUN 4.0.3. We were all quite happy that it worked, and we moved tons of files from the little file server onto the SUN. During this time, it has performed flawlessly, until the last couple of days. Whenever something is copied to or from the AUFS volume, we get a message that "The file "xxx..." cannot be opened/printed (file/folder is locked)." Why is this happening? On the Unix side, I can create files in those directories, delete them, etc., so this does not really seem to be a disk problem. I only have 4 or 5 files on my volume, and I haven't changed anything since the last time it worked. There are only 6 people who use AUFS (the limit in the log file says it is 10). I have checked the log file for strange things, but I haven't found any, yet. (Oops! Forgot about that log file for 2 months. It's a little large. Restarting with a zero length log file does not change anything.) /etc/start-cap-servers has been in rc.local for a long time, and everything seems to start up and work just fine until someone tries to get something from a volume or put it on a volume. Any nifty explanations would be great! Better yet, how can I fix it?!! Thanks. Russell mosemann@hoss.unl.edu uunet!hoss.unl.edu!mosemann
mosemann@hoss.unl.edu (Russell Mosemann) (08/17/90)
My problem is solved. It turns out that the lock daemon was not running. Whenever anyone tried to perform an operation on a file, AUFS must lock it, do he operation, and unlock the file. Since the lock request was failing, the files were being interpreted as locked. Something bombed in rc.local at startup and several other important daemons were also missing. Thanks to casper@fwi.uva.nl for the suggestions. Russell Mosemann mosemann@hoss.unl.edu uunet!hoss.unl.edu!mosemann