On Sat, May 1, 2010 at 2:25 AM, Brandon S. Allbery KF8NH
wrote:
> On Apr 30, 2010, at 18:07 , Andrew Deason wrote:
>>
>> After some offline discussion, this appears to probably be the case.
>> sqlite opens the db file O_RDONLY, and attempts to acquire an fcntl
>> F_WRLCK on it, to which it gets ER
On May 1, 2010, at 02:25 , Brandon S. Allbery KF8NH wrote:
EACCES is the POSIX-specified errno.
My bad; it is indeed EBADF, EACCES is only returned if the region is
already locked.
--
brandon s. allbery [solaris,freebsd,perl,pugs,haskell] allb...@kf8nh.com
system administrator [openafs,hei
On Apr 30, 2010, at 18:07 , Andrew Deason wrote:
After some offline discussion, this appears to probably be the case.
sqlite opens the db file O_RDONLY, and attempts to acquire an fcntl
F_WRLCK on it, to which it gets EROFS back. Trying to acquire a
writelock on a file opened readonly doesn't mak
> After some offline discussion, this appears to probably be the case.
> sqlite opens the db file O_RDONLY, and attempts to acquire an fcntl
> F_WRLCK on it, to which it gets EROFS back. Trying to acquire a
> writelock on a file opened readonly doesn't make a lot of sense to me;
> can someone tell
On 26 Apr 2010, at 19:39, Adam Megacz wrote:
>
> Jeffrey Altman writes:
>> When a whole file lock is write-held, all of the dirty data in the cache
>> must be written back to the file server before the lock is released.
>> This is currently not being done and as a result, the database becomes
>
the best way to know it's fixed? watch the release announcements. it's
not like we're going to be coy about it.
On Mon, Apr 26, 2010 at 2:39 PM, Adam Megacz wrote:
>
> Jeffrey Altman writes:
>> When a whole file lock is write-held, all of the dirty data in the cache
>> must be written back to th
On 26 Apr 2010, at 04:18, Brandon S. Allbery KF8NH wrote:
>>
>> If I understand Simon correctly, clients are also not getting file
>> updates while the file is opened O_RDWR. That would still seem to be a
>> problem even if we flush on unlock.
>
> Flushing will update the server, which will brea
On Apr 25, 2010, at 23:00 , Andrew Deason wrote:
On Sun, 25 Apr 2010 21:19:24 -0400
Jeffrey Altman wrote:
When a whole file lock is write-held, all of the dirty data in the
cache must be written back to the file server before the lock is
released. This is currently not being done and as a resul
On 4/24/2010 4:23 PM, Adam Megacz wrote:
> Me too, but my hopes are not high. The fact that the databases become
> corrupted when using whole-file locks only suggests that there is a more
> subtle problem lurking here.
>
Actually it is a well understood problem. I just didn't realize that
the
On Mon, Apr 19, 2010 at 10:55 AM, Andrew Deason wrote:
> On Mon, 19 Apr 2010 09:41:06 -0600
> Ken Dreyer wrote:
>> flock - Whole-file locking. This completely hung on Solaris when
>> opening sqlite files on read-only mounts. Even if the SQLite
>> operations were read-only (SELECT, etc), PHP hung.
10 matches
Mail list logo
