On Sat, Jan 19, 2013 at 6:52 AM, Stephan Beal wrote:
> On Fri, Jan 18, 2013 at 9:56 PM, Joseph Mingrone wrote:
>>
>> What's the equivalent of a
>> virtual beer/coffee/tea/etc?
>
>
> How about a HOWTO doc to save the next guy some pain ;).
I think it would be pretty short: If you are using fossi
On Fri, Jan 18, 2013 at 9:56 PM, Joseph Mingrone wrote:
> What's the equivalent of a
> virtual beer/coffee/tea/etc?
>
How about a HOWTO doc to save the next guy some pain ;).
--
- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
__
Richard, Martin, Matt and Baptiste;
On Thu, Jan 17, 2013 at 5:58 PM, Martin S. Weber wrote:
> Wild guess: are you running your rpc services, lockd and statd amongst them?
> (server? client?)
On Thu, Jan 17, 2013 at 7:23 PM, Baptiste Daroussin
wrote:
> Your failure is the following: fcntl(4,F_S
On Thu, Jan 17, 2013 at 6:23 PM, Baptiste Daroussin <
baptiste.darous...@gmail.com> wrote:
> 2013/1/18 Joseph Mingrone :
> > On Thu, Jan 17, 2013 at 7:03 PM, Richard Hipp wrote:
> >> I don't know why not... Did you start from fresh sources? What did
> you do
> >> to get the error below?
> >
> >
2013/1/18 Joseph Mingrone :
> On Thu, Jan 17, 2013 at 7:03 PM, Richard Hipp wrote:
>> I don't know why not... Did you start from fresh sources? What did you do
>> to get the error below?
>
> Apparently I didn't start from fresh sources or I messed something
> else up. After...
>
> tar -xf tar -
On Thu, Jan 17, 2013 at 7:21 PM, Joseph Mingrone wrote:
> fossil init blah
>
Make that
./fossil init blah
and I get the same error.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listin
On Thu, Jan 17, 2013 at 7:03 PM, Richard Hipp wrote:
> I don't know why not... Did you start from fresh sources? What did you do
> to get the error below?
Apparently I didn't start from fresh sources or I messed something
else up. After...
tar -xf tar -xvf fossil-src-20121022124804.tar.gz
cd
Hello Baptiste;
On Thu, Jan 17, 2013 at 7:02 PM, Baptiste Daroussin
wrote:
> Can you host somewhere the file.out created by truss -o file.out
> fossil init bla ?
>
Sure. http://gly.ath.cx/misc/file.out
Joseph
___
fossil-users mailing list
fossil-users
On Thu, Jan 17, 2013 at 6:00 PM, Joseph Mingrone wrote:
> On Thu, Jan 17, 2013 at 6:24 PM, Richard Hipp wrote:
> > Please try again using the patch to Fossil I just now checked in:
> >
> > http://www.fossil-scm.org/fossil/info/7536c6aea5
>
> It didn't compile for me.
>
I don't know why not.
2013/1/18 Joseph Mingrone :
> On Thu, Jan 17, 2013 at 6:24 PM, Richard Hipp wrote:
>> Please try again using the patch to Fossil I just now checked in:
>>
>> http://www.fossil-scm.org/fossil/info/7536c6aea5
>
> It didn't compile for me.
>
> ...
> cc -g -O2 -DHAVE_AUTOCONFIG_H -I. -I./src -Ibl
On Thu, Jan 17, 2013 at 6:24 PM, Richard Hipp wrote:
> Please try again using the patch to Fossil I just now checked in:
>
> http://www.fossil-scm.org/fossil/info/7536c6aea5
It didn't compile for me.
...
cc -g -O2 -DHAVE_AUTOCONFIG_H -I. -I./src -Ibld -o bld/db.o -c bld/db_.c
./src/db.c: In
On Thu, Jan 17, 2013 at 6:38 PM, Matt Welland wrote:
> Do things such as a kernel compile, video editing or other disk intensive
> tasks work fine?
It's only been a few weeks, but all IO seems fine. I did some IO
testing with IOR (http://sourceforge.net/projects/ior-sio/) and it
looked OK.
% ./
This problem doesn't look much like an issue with fossil itself. Perhaps
trying a filesystem test suite would give you some hints as to the root
cause? Google provided this link that might be a good starting point:
http://nfsv4.bullopensource.org/doc/testing_tools.php
Do things such as a kernel co
The test user I created, whose home directory is set to the new
filesystem with access times turned on, is also having the sqlite
problems now.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailma
On Thu, Jan 17, 2013 at 6:18 PM, Richard Hipp wrote:
> fossil init blah --sqltrace
% fossil init blah --sqltrace
fossil: SQLITE_IOERR: statement aborts at 1: [BEGIN EXCLUSIVE] disk I/O error
fossil: SQLITE_IOERR: disk I/O error
fossil: disk I/O error
If you have recently updated your fossil exec
On Thu, Jan 17, 2013 at 5:11 PM, Joseph Mingrone wrote:
> On Thu, Jan 17, 2013 at 5:52 PM, Richard Hipp 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.
> >
On Thu, Jan 17, 2013 at 4:13 PM, Joseph Mingrone wrote:
> Hello all;
>
> I'm seeing errors like this.
>
> % fossil init blah
> fossil: SQLITE_IOERR: statement aborts at 1: [BEGIN EXCLUSIVE] disk
> I/O error
> fossil: SQLITE_IOERR: disk I/O error
> fossil: disk I/O error
>
What does the followin
On Thu, Jan 17, 2013 at 5:52 PM, Richard Hipp 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
>
>
On 01/17/13 16:46, Joseph Mingrone wrote:
One change I made when I upgraded the box was that I set home
directories to be nfs mounted from a storage server. I'm using the
automount daemon to do the mounting. Before home directories were
local. To test if this was causing a problem I created a
On Thu, Jan 17, 2013 at 4:46 PM, Joseph Mingrone wrote:
> One change I made when I upgraded the box was that I set home
> directories to be nfs mounted from a storage server. I'm using the
> automount daemon to do the mounting. Before home directories were
> local. To test if this was causing
On Thu, Jan 17, 2013 at 5:46 PM, Richard Hipp wrote:
> And, you say, it was working fine on the previous version of FreeBSD? What
> version did you upgrade from?
It was working fine on the previous version, which was 8.3. It's also
working fine on other machines running 9.1-RELEASE, but with lo
One change I made when I upgraded the box was that I set home
directories to be nfs mounted from a storage server. I'm using the
automount daemon to do the mounting. Before home directories were
local. To test if this was causing a problem I created a new user
with a local home directory. This
On Thu, Jan 17, 2013 at 4:35 PM, Joseph Mingrone wrote:
> I should also mention that everything seems to work fine when I run
> fossil as root, but not with sudo. It doesn't appear to be anything
> specific to my environment because the same problem occurs with other
> users on the box.
>
And,
I should also mention that everything seems to work fine when I run
fossil as root, but not with sudo. It doesn't appear to be anything
specific to my environment because the same problem occurs with other
users on the box.
Joseph
___
fossil-users maili
On Thu, Jan 17, 2013 at 5:25 PM, Richard Hipp wrote:
> Have you tried compiling Fossil yourself from sources? (It isn't hard.)
Yes. Same result.
Joseph
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/c
On Thu, Jan 17, 2013 at 4:13 PM, Joseph Mingrone wrote:
> Hello all;
>
> I'm seeing errors like this.
>
> % fossil init blah
> fossil: SQLITE_IOERR: statement aborts at 1: [BEGIN EXCLUSIVE] disk
> I/O error
> fossil: SQLITE_IOERR: disk I/O error
> fossil: disk I/O error
>
> I just upgraded to Fre
Hello all;
I'm seeing errors like this.
% fossil init blah
fossil: SQLITE_IOERR: statement aborts at 1: [BEGIN EXCLUSIVE] disk
I/O error
fossil: SQLITE_IOERR: disk I/O error
fossil: disk I/O error
If you have recently updated your fossil executable, you might
need to run "fossil all rebuild" to
27 matches
Mail list logo
