On Mon, Jul 15, 2013 at 2:08 PM, Richard Hipp <d...@sqlite.org> wrote:
> > > On Mon, Jul 15, 2013 at 7:39 AM, Stephan Beal <sgb...@googlemail.com>wrote: > >> Hi, all, >> >> i have just installed a fossil repo on a company-internal Linux server >> and i am seeing a weird new error message at the top of all pages: >> >> error code 28: file renamed while open: /.../bss-scripts.fsl >> > > This is a warning message that the SQLite core issues if the inode number > of the database file changes. A change in the inode number can be an > indicator that a database file has been renamed while it is in use, which > can lead to database corruption. Or, it might just indicate that the > database is on NFS. > > You'll be much much happier with the performance if you put the repository > on a local filesystem, btw. > i would rather gnaw off my foot than hassle with having a DB on an NFS, i just wasn't aware until after the fact that i was even on NFS :/. So, problem solved by simply moving the repo file into the local FS. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
