Re: [sqlite] oserror-2.1.x fails when run on an BTRFS volume - directories may have any st_size.

2019-12-27 Thread Stefan Brüns
On Donnerstag, 26. Dezember 2019 02:01:36 CET Richard Hipp wrote: > Tnx for the report. Should be fixed as of > https://sqlite.org/src/info/c8c6dd0e6582ec91 > > Please do us the favor of trying this out on both Btrfs and XFS and > making sure it works correctly on both filesystems. Tnx. Thanks

Re: [sqlite] oserror-2.1.x fails when run on an BTRFS volume - directories may have any st_size.

2019-12-25 Thread Richard Hipp
Tnx for the report. Should be fixed as of https://sqlite.org/src/info/c8c6dd0e6582ec91 Please do us the favor of trying this out on both Btrfs and XFS and making sure it works correctly on both filesystems. Tnx. On 12/25/19, Stefan Brüns wrote: > The oserror-2.1.1 test fails, as a exisiting

[sqlite] oserror-2.1.x fails when run on an BTRFS volume - directories may have any st_size.

2019-12-25 Thread Stefan Brüns
The oserror-2.1.1 test fails, as a exisiting test.db-wal is silently ignored. Running this small example on e.g. XFS or tmpfs yields the following: $> mkdir test.db-wal $> strace -efile sqlite3 test.db ... sqlite> .databases openat(AT_FDCWD, "test.db", O_RDONLY) = -1 ENOENT (Datei oder