Documentation Source Text

Check-in [63ad7e56b1]
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Revise the description of the Tcler's wiki database corruption event.
Downloads: Tarball | ZIP archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: 63ad7e56b197282573d256795d80ae63826a3998
User & Date: drh 2013-10-08 15:07:16.256
Context
2013-10-11
14:18
Edits to the change log. (check-in: c508b3c51a user: drh tags: trunk)
2013-10-08
15:07
Revise the description of the Tcler's wiki database corruption event. (check-in: 63ad7e56b1 user: drh tags: trunk)
2013-10-07
08:27
Add documentation on the optional timezone suffixes to timestrings in the date and time functions. (check-in: d4924d1139 user: drh tags: trunk)
Changes
Unified Diff Ignore Whitespace Patch
Changes to pages/howtocorrupt.in.
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
<h3>6.3 Filesystem Corruption</h3>

<p>Since SQLite databases are ordinary disk files, any malfunction in the
filesystem can corrupt the database.  Filesystems in modern operating systems
are very reliable, but errors do still occur.  For example, on 2013-10-01
the SQLite database that holds the
<a href="http://wiki.tcl.tk/">Wiki for Tcl/Tk</a> went corrupt a few days
after an erroneous attempt to increase the size of an EXT3 partition caused
the filesystem to begin malfunctioning.  In that event, the filesystem
eventually became so badly corrupted that the machine was unusable and
had to be rebuilt.  But the earliest symptom of trouble was the corrupted
SQLite database.</p>

<h2>7.0 Bugs in SQLite</h2>

<p>SQLite is [testing | very carefully tested] to help ensure that it is
as bug-free as possible.  Among the many tests that are carried out for
every SQLite version are tests that simulate power failures, I/O errors,
and out-of-memory (OOM) errors and verify that no database corrupt occurs







|
|
|
|
<







372
373
374
375
376
377
378
379
380
381
382

383
384
385
386
387
388
389
<h3>6.3 Filesystem Corruption</h3>

<p>Since SQLite databases are ordinary disk files, any malfunction in the
filesystem can corrupt the database.  Filesystems in modern operating systems
are very reliable, but errors do still occur.  For example, on 2013-10-01
the SQLite database that holds the
<a href="http://wiki.tcl.tk/">Wiki for Tcl/Tk</a> went corrupt a few days
after the host computer was moved to a dodgy build of the (linux) kernel
that had issues in the filesystem layer.  In that event, the filesystem
eventually became so badly corrupted that the machine was unusable, but
the earliest symptom of trouble was the corrupted SQLite database.</p>


<h2>7.0 Bugs in SQLite</h2>

<p>SQLite is [testing | very carefully tested] to help ensure that it is
as bug-free as possible.  Among the many tests that are carried out for
every SQLite version are tests that simulate power failures, I/O errors,
and out-of-memory (OOM) errors and verify that no database corrupt occurs