Do a "sum" on the files to make sure they are identical. #1 Show all the files in the directorty #2 How are you copying? Basically...show us ALL the commands and files you are using... Michael D. Black Senior Scientist Advanced Analytics Directorate Northrop Grumman Information Systems
________________________________ From: sqlite-users-boun...@sqlite.org on behalf of Pirmin Walthert Sent: Fri 11/12/2010 6:42 AM To: sqlite-users@sqlite.org Subject: EXTERNAL:Re: [sqlite] Strange corruptions Am 12.11.2010 13:06, schrieb Simon Slavin: > On 12 Nov 2010, at 7:55am, Pirmin Walthert wrote: > >> Some months ago we changed to uclibc-git (nptl support), kernel >> 2.6.32.X, busybox> 1.16 and at the moment sqlite 3.7.2. > Are you accessing your databases straight from a hard disk or across a > network mount ? > > Please tell us the filing system (either hard disk FS or network FS) you're > using. > > Simon. > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users Both (the one with the source and the one with the dst database) are local (ext3 loopback fs). I doubt that it has to do with the FS because if do the following, the same thing happens: - copy the corrupted DB to /tmp (tmpfs) - checking the db with sqlite3 /tmp/baddb "PRAGMA integrity_check;" => this still shows me ok - making a backup of /tmp/baddb to /tmp/backupdb (or whatever) - checking the destionation db now gives me the same errors again Pirmin _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
_______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
