Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
If the raw file containing your database is represented inside the structures used by a filesystem and something in the filesystem gets trashed, having a journaled database isn't going to help at all because the journaling information will be inaccessible, since it's also stored in the trashed filesystem. So, if you store your database inside a filesystem, double journaling is unavoidable if you want your data safe. The preferable alternative is to avoid the structures involved in a filesystem, and allocate an entire partition to your database. Then all you have to worry about is if the partition table were to get trashed, so make a backup of block 0 of the disk. Mark R. [hidden email] wrote: > IMHO: > EXT2 is great for a database journal in that you won't be double > journalling. (I often speculate that a very minimal UNIX file system > designed for purely for speed and regularly sized blocks, something like a > streamlined FAT system, would be awesome for databases.) -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ Discuss mailing list [hidden email] http://lists.blu.org/mailman/listinfo/discuss
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |