[sqlite] sqlite error code 1034

2015-06-23 Thread Simon Slavin
On 23 Jun 2015, at 8:49pm, Mayank Kumar (mayankum) wrote: > Thanks all for the useful inputs. One more question I have is can the 1034 > error code ever mean that disk is full or nvram is full and hence it cannot > fsync ? The error for 'disk full' should never happen at fsync(). It should

[sqlite] sqlite error code 1034

2015-06-23 Thread Mayank Kumar (mayankum)
fails . Can that happen ? -Original Message- From: sqlite-users-bounces at mailinglists.sqlite.org [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On Behalf Of Scott Doctor Sent: Tuesday, June 23, 2015 3:33 AM To: General Discussion of SQLite Database Subject: Re: [sqlite] sqlite

[sqlite] sqlite error code 1034

2015-06-23 Thread Nico Williams
On Tue, Jun 23, 2015 at 09:12:31PM +0100, Simon Slavin wrote: > On 23 Jun 2015, at 8:49pm, Mayank Kumar (mayankum) > wrote: > > Thanks all for the useful inputs. One more question I have is can > > the 1034 error code ever mean that disk is full or nvram is full and > > hence it cannot fsync ? >

[sqlite] sqlite error code 1034

2015-06-23 Thread Dan Kennedy
sts.sqlite.org] On Behalf Of Simon > Slavin > Sent: Monday, June 22, 2015 6:11 PM > To: General Discussion of SQLite Database > Subject: Re: [sqlite] sqlite error code 1034 > > > On 23 Jun 2015, at 1:33am, Mayank Kumar (mayankum) > wrote: > >> We once in a while s

[sqlite] sqlite error code 1034

2015-06-23 Thread Simon Slavin
On 23 Jun 2015, at 6:01am, Mayank Kumar (mayankum) wrote: > Do you think if sqlite3_step or sqlite3_open fail with this error, we should > treat this as transaction committed and ignore the fsync error and it will be > retried with the next commit or read and eventually will sync unless I see

[sqlite] sqlite error code 1034

2015-06-23 Thread Mayank Kumar (mayankum)
users-boun...@mailinglists.sqlite.org] On Behalf Of Simon Slavin Sent: Monday, June 22, 2015 6:11 PM To: General Discussion of SQLite Database Subject: Re: [sqlite] sqlite error code 1034 On 23 Jun 2015, at 1:33am, Mayank Kumar (mayankum) wrote: > We once in a while see the following errors returns by

[sqlite] sqlite error code 1034

2015-06-23 Thread Scott Doctor
An fsync error with nvram may be caused by a timeout during the write cycle. write cycles in nvram can be many times longer than a read cycle in this type of memory. Trying to write a large buffer of data may take multiple seconds especially if adresses are non-linear depending on size and tec

[sqlite] sqlite error code 1034

2015-06-23 Thread Simon Slavin
On 23 Jun 2015, at 1:33am, Mayank Kumar (mayankum) wrote: > We once in a while see the following errors returns by sqlite for a database > created on nvram. I am trying to understand, how are other users handling > this error ? if fsync fails and sqlite api fails because of this issue, does

[sqlite] sqlite error code 1034

2015-06-23 Thread Mayank Kumar (mayankum)
Hi Sqlite users We once in a while see the following errors returns by sqlite for a database created on nvram. I am trying to understand, how are other users handling this error ? if fsync fails and sqlite api fails because of this issue, does sqlite internally retry before declaring it cannot c