| Summary: | Odd symlink problem on Solaris | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Anand Avati <aavati> |
| Component: | posix | Assignee: | Anand Avati <aavati> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 2.0.3 | CC: | chrisw, gluster-bugs, shehjart |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Solaris | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | --- | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
This might be our setup but I thought I should mention it. We have three machines in a gluster -- two CentOS 5 machines running 3.0.0 RPMS and a Solaris 10 machine running the latest version (yesterday) from the GIT repository. The Solaris machine uses a ZFS partition so we can take snapshots of what is going on on the other machines (which are development machines). Issues are arising with files which are symlinked into the gluster which are outside the gluster but do not exist on the Solaris machine. I can replicate the problem like this: mkdir fred cd fred ln -s /var/tmp/this-does-not-exist ls -l shows no files ls -l this-does-not-exist lrwxrwxrwx 1 shb widearea 28 Feb 8 13:07 this-does-not-exist -> /var/tmp/this-does-not-exist and on the Solaris machine we get the error: [2010-02-08 13:07:51] E [posix.c:1834:posix_symlink] posix: lstat failed on /common/fred/this-does-not-exist: No such file or directory I can 'cure' the problem by removing the Solaris machine and I cannot duplicate this on our other, pure CentOS, gluster. This looks like a Solaris issue but I cannot see why from looking at the code. I guess the real question is whether any one else can reproduce this bug using Solaris or whether (as it is quite weird) something to do with us. TIA Simon.------ Wide Area Communications www.widearea.co.uk