From: Rolf Campbell <rcampbell-cygwin@dragonwaveinc.com>
To: cygwin@cygwin.com
Subject: Re: cygwin 1.7.15: svn disk I/O error
Date: Tue, 19 Jun 2012 19:24:00 -0000 [thread overview]
Message-ID: <jrqjko$dc3$1@dough.gmane.org> (raw)
In-Reply-To: <CE9C056E12502146A72FD81290379E9A4361BBA1@ENFIRHMBX1.datcon.co.uk>
On 2012-06-19 05:29, Adam Dinwoodie wrote:
> Rolf Campbell wrote:
>> $ svn up
>> Updating '.':
>> svn: E200030: disk I/O error, executing statement 'RELEASE s6'
>> svn: E200030: sqlite: unable to open database file
>> svn: E200030: sqlite: unable to open database file
>>
>> $ svn cleanup
>> svn: E200030: disk I/O error, executing statement 'RELEASE s79'
>>
>> <snip>
>
> I've had the same problem, and have found a solution: this appears for me to be an interaction with TortoiseSVN, which I have on my machine and which is entirely unaware of Cygwin.
> Disabling TortoiseSVN's icon cache has completely resolved the issue for me. You can do this by running TortoiseSVN's Settings program, going to "Icon Overlays", and selecting "None" under "Status cache", then hitting Apply.
> That may explain why Rolf's been hitting this despite apparently having no AV installed.
> Adam
That's a very interesting discovery. I certainly am using TortoiseSVN.
There must be some interaction between the most recent version of
sqlite and TortoiseSVN's status scanner. I've been playing around with
sqlite versions and I've confirmed what others have stated that it's
only a problem with v3.7.12.1 and NOT a problem with v3.7.3.
I've upgraded back to v3.7.12.1 and disabled TortoiseSVN's icon scanner.
It appears to resolve the problem for me as well.
I would hate to add TortoiseSVN to the BLODA.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2012-06-19 19:24 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-14 19:48 Rolf Campbell
2012-06-14 19:55 ` Christopher Faylor
2012-06-14 20:09 ` Rolf Campbell
2012-06-14 22:00 ` Garrison, Jim (ETW)
2012-06-14 22:02 ` Garrison, Jim (ETW)
2012-06-15 10:38 ` Warren Young
2012-06-15 13:24 ` Rolf Campbell
2012-06-15 13:43 ` Rolf Campbell
2012-06-19 9:32 ` Adam Dinwoodie
2012-06-19 19:24 ` Rolf Campbell [this message]
2012-06-19 21:19 ` Achim Gratz
2012-06-20 0:22 ` Warren Young
2012-06-20 5:25 ` Achim Gratz
2012-06-26 16:46 ` Achim Gratz
2012-06-26 17:25 ` David Rothenberger
2012-06-26 18:07 ` Achim Gratz
2012-06-27 9:11 ` Adam Dinwoodie
2012-06-27 14:07 ` Achim Gratz
2012-06-27 18:18 ` David Rothenberger
2012-06-27 18:41 ` Achim Gratz
2012-06-28 11:49 ` Achim Gratz
2012-06-28 16:31 ` David Rothenberger
2012-06-28 19:04 ` Achim Gratz
2012-06-28 19:27 ` David Rothenberger
2012-06-28 20:40 ` Achim Gratz
2012-07-11 6:34 ` Achim Gratz
2012-07-11 7:07 ` marco atzeri
2012-07-11 7:48 ` Achim Gratz
2012-07-11 17:19 ` marco atzeri
2012-06-28 17:37 ` Rolf Campbell
2012-06-28 19:11 ` Achim Gratz
2012-06-28 20:03 ` Warren Young
2012-06-28 20:35 ` Achim Gratz
2012-06-28 21:17 ` Warren Young
2012-06-28 20:37 ` David Rothenberger
[not found] <CABVhxxKw8i96668GgHmMyPXCn+nBS8S874Q7wSSHgoer8iiSsw@mail.gmail.com>
2012-08-07 1:10 ` Michael Gundlach
2012-08-07 1:55 ` Warren Young
2012-08-07 1:57 ` Michael Gundlach
2012-08-07 2:42 ` Warren Young
2012-08-07 12:16 ` Michael Gundlach
2012-08-07 17:56 ` David Rothenberger
2012-08-08 13:14 ` Warren Young
2012-08-07 7:00 ` Achim Gratz
2012-08-07 7:38 ` Warren Young
2012-08-07 5:07 ` Christopher Faylor
[not found] ` <CABVhxxJ_nsTF3o85nWJsRdMOq38LYr2R9b9H8ATHfNCCqnmbqw@mail.gmail.com>
2012-08-07 14:05 ` Michael Gundlach
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='jrqjko$dc3$1@dough.gmane.org' \
--to=rcampbell-cygwin@dragonwaveinc.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).