Hide Forgot
Installed 3.1.4 from deb on two Ubuntu 10.10 systems, which went smoothly. Then built 3.1.4 from tar for an Ubuntu 8.04.4 system (because the glibc is too old for the deb), which seemed to build and install without issue (other than needing to run ldconfig after the install). While the gluster file system can mount with NFS just fine from the 8.04 box, trying the same filesystem as a glusterfs mount results in 100% CPU usage, and no output when even just trying to list the mounted directory.
(In reply to comment #0) > Installed 3.1.4 from deb on two Ubuntu 10.10 systems, which went smoothly. Then > built 3.1.4 from tar for an Ubuntu 8.04.4 system (because the glibc is too old > for the deb), which seemed to build and install without issue (other than > needing to run ldconfig after the install). While the gluster file system can > mount with NFS just fine from the 8.04 box, trying the same filesystem as a > glusterfs mount results in 100% CPU usage, and no output when even just trying > to list the mounted directory. Please provide the log files and exact setup details.
(In reply to comment #1) > Please provide the log files and exact setup details. This was a very generic setup, following your wiki, with whatever the default logging is. It wasn't set at a debug log level. If you expect there's info in the logs that will help you debug this, please specify where and what to look for. Since the result was that the gluster client doesn't work when built on Ubuntu 8.04.4, while nfs works fine, and since I had a pressing need to put this into production (failing storage elsewhere to work around), I did, with nfs. My bet is if you build gluster 3.1.4 on Ubuntu 8.04.4 and try to use the client to mount a 2-note replicated glusterfs system you'll see exactly what I did. But I don't have a test system with 8.04.4 to play with, to try to duplicate the problem myself. The system it showed up on is in production, so I can't screw with it to get more debug data on this. Still, if you think it will have logged something - or that the file servers will have - I'll be happy to dig that out for you. Just tell me what to look for. I didn't find anything on a quick look when the bug was manifesting.
Hi Whit, do you still see the same problem? if yes, please provide us with logs in /usr/local/var/log/glusterfs directory to help solve this problem. the client log file is the one with <mount-point>.log name
Rajesh, No opportunity to test, since went to NFS mounting in this case, which works fine. As I said before the systems are in production. Don't have any other Ubuntu 8.04 boxes to build Gluster on, and will be upgrading the OS on the ones where I saw this bug soon. Whit
More focus on 3.3.0 release as of now, so taking the priority down. Please let us know how critical is this for you. Will consider the priority re-assignment after 3.3.0beta release based on your feedback.