On Thu, Jan 17, 2013 at 5:11 PM, Joseph Mingrone <j...@ftfl.ca> wrote:
> On Thu, Jan 17, 2013 at 5:52 PM, Richard Hipp <d...@sqlite.org> wrote:
> > That's a good clue. It makes me think this is probably an NFS problem,
> > perhaps related to posix advisory locking and your NFS implementations'
> > inability to support it.
> >
> > Try setting:
> >
> > export FOSSIL_VFS=unix-dotfile
> >
> > or
> >
> > export FOSSIL_VFS=unix-none
>
> Setting FOSSIL_VFS didn't help.
>
Please try again using the patch to Fossil I just now checked in:
http://www.fossil-scm.org/fossil/info/7536c6aea5
>
> The storage server is running zfs. When I created the filesystem for
> the home directories I turned off access times. Here is the full
> command I used to create the file system:
> zfs create -o atime=off -o compression=on -o -o
> sharenfs="maproot=root,network 192.168.0.0,mask 255.255.255.0"
> tank/home.
>
> I just created a new zfs filesystem on the server but I didn't turn
> off the access times. I then created a new user whose home directory
> was set to this new file system. This user can run fossil without any
> problems. I put access times a back on for tank/home (the filesystem
> all other users except root have as their home directory), but those
> users still have the fossil errors.
>
> On Thu, Jan 17, 2013 at 5:58 PM, Martin S. Weber <martin.we...@nist.gov>
> wrote:
> > Wild guess: are you running your rpc services, lockd and statd amongst
> them?
> > (server? client?)
> >
>
> Both the client are server are running rpcbind and mountd.
>
> Joseph
> _______________________________________________
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
--
D. Richard Hipp
d...@sqlite.org
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
