Re: [sqlite] Potential bug: Database on gvfs mount cannot be committed to

2016-09-18 Thread Simon Slavin
On 19 Sep 2016, at 2:52am, Keith Medcalf wrote: > That is to say there is no difference between a block device (such as a > physical hard disk) attached to the computer via a 1 foot SCSI cable and an > iSCSI LUN where the iSCSI block device is located on a different

Re: [sqlite] Potential bug: Database on gvfs mount cannot be committed to

2016-09-18 Thread Keith Medcalf
No database server product of which I am aware will "work" properly when the database resides on a remote filesystem. There is a *vast* difference between a "remote file system" and a "local file system on a remote block device". There is no difference between a "remote block device" known as

Re: [sqlite] Potential bug: Database on gvfs mount cannot be committed to

2016-09-18 Thread Stephen Chrzanowski
"snapshotable" or not, DBs are accessed from the local file system, not from a network where another OS has control of the file system. On Sun, Sep 18, 2016 at 10:16 AM, Florian Weimer wrote: > * R. Smith: > > > Enterprise DBs have servers on the same machine as the Files

Re: [sqlite] Potential bug: Database on gvfs mount cannot be committed to

2016-09-18 Thread Florian Weimer
* R. Smith: > Enterprise DBs have servers on the same machine as the Files they > access, they do not actually use the network file-system to access the > DB data-files over the network from multiple clients, or even servers > (unless the DBs are partitioned so and ONLY accessed by the single >

[sqlite] Potential bug: Database on gvfs mount cannot be committed to

2015-09-12 Thread R.Smith
On 2015-09-12 06:30 PM, Florian Weimer wrote: >> On 09/06/2015 11:13 AM, Florian Weimer wrote: >>> Surely that's not true, and NFS and SMB are fine as long as there >>> is no concurrent access? >> And no program crashes, no network glitches, no optimisation in the >> protocols to deal with

[sqlite] Potential bug: Database on gvfs mount cannot be committed to

2015-09-12 Thread Florian Weimer
* Roger Binns: > On 09/06/2015 11:13 AM, Florian Weimer wrote: >> Surely that's not true, and NFS and SMB are fine as long as there >> is no concurrent access? > > And no program crashes, no network glitches, no optimisation in the > protocols to deal with latency, nothing else futzing with the

[sqlite] Potential bug: Database on gvfs mount cannot be committed to

2015-09-06 Thread Dan Kennedy
On 09/06/2015 09:23 PM, Roger Binns wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 09/06/2015 06:16 AM, Markus Weiland wrote: >> I've discovered a potential bug in handling of SQLite database >> files on gvfs mounted network shares. > SQLite doesn't support being stored on the

[sqlite] Potential bug: Database on gvfs mount cannot be committed to

2015-09-06 Thread Simon Slavin
On 6 Sep 2015, at 9:16pm, Roger Binns wrote: > no programs futzing with them (backup agents, virus scanners etc) Reminds me of my most annoying SQLite problem. They were running a virus scanner which delayed temp file deletion and SQLite could not manage its journal files properly. Took me

[sqlite] Potential bug: Database on gvfs mount cannot be committed to

2015-09-06 Thread Florian Weimer
* Roger Binns: > On 09/06/2015 06:16 AM, Markus Weiland wrote: >> I've discovered a potential bug in handling of SQLite database >> files on gvfs mounted network shares. > > SQLite doesn't support being stored on the network for several > reasons, including that network file protocols don't

[sqlite] Potential bug: Database on gvfs mount cannot be committed to

2015-09-06 Thread Markus Weiland
I see. Since this was working under Ubuntu 14.04, I assume this is a regression with gvfs. I'll check over there. On 2015-09-06 06:00 PM, sqlite-users-request at mailinglists.sqlite.org wrote: > On 09/06/2015 06:16 AM, Markus Weiland wrote: >> >I've discovered a potential bug in handling of

[sqlite] Potential bug: Database on gvfs mount cannot be committed to

2015-09-06 Thread Markus Weiland
Hi, I've discovered a potential bug in handling of SQLite database files on gvfs mounted network shares. Steps to reproduce: 1. Under vanilla Ubuntu 15.04 with latest official patches and SQLite version 2.8.17, mount a Windows / SMB network share via Nautilus file manager. The share can be

[sqlite] Potential bug: Database on gvfs mount cannot be committed to

2015-09-06 Thread Roger Binns
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/06/2015 11:13 AM, Florian Weimer wrote: > Surely that's not true, and NFS and SMB are fine as long as there > is no concurrent access? And no program crashes, no network glitches, no optimisation in the protocols to deal with latency, nothing

[sqlite] Potential bug: Database on gvfs mount cannot be committed to

2015-09-06 Thread Roger Binns
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/06/2015 10:20 AM, Markus Weiland wrote: > I see. Since this was working under Ubuntu 14.04, I assume this is > a regression with gvfs. I'll check over there. Nope. SQLite can not maintain data integrity when used with *any* network filesystem.

[sqlite] Potential bug: Database on gvfs mount cannot be committed to

2015-09-06 Thread Roger Binns
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/06/2015 06:16 AM, Markus Weiland wrote: > I've discovered a potential bug in handling of SQLite database > files on gvfs mounted network shares. SQLite doesn't support being stored on the network for several reasons, including that network file