Date: Fri, 17 Jun 2005 18:20:59 +0200 From: Matthias Buelow <mkb@incubus.de> To: David Sze <dsze@distrust.net> Cc: freebsd-stable@freebsd.org, Greg Barniskis <nalists@scls.lib.wi.us>, uzi@bmby.com, Matthias Buelow <mkb@incubus.de> Subject: Re: FreeBSD MySQL still WAY slower than Linux Message-ID: <200506171620.j5HGKxwW042819@drjekyll.mkbuelow.net> In-Reply-To: Message from David Sze <dsze@distrust.net> of "Fri, 17 Jun 2005 10:59:38 CDT." <20050617155938.GB94284@mail.distrust.net>
next in thread | previous in thread | raw e-mail | index | archive | help
David Sze <dsze@distrust.net> writes: >CentOS uses ext3 by default. How does having a journal help if the >journal is stored on the same async filesystem? Unless the journal >writes are guaranteed sync. The journal guarantees that the filesystem will always be consistent. If a journal entry doesn't make it to disk, the operation has never happened; and the journal entry won't get removed, until the metadata update has been performed. So the worst thing that could happen is, that the same operation will be performed twice, once normally, and once at log replay on reboot. This is not an issue, since such metadata operations (delete file from directory, write a value into superblock, etc.) are usually idempotent. That's the basic function of all journalled filesystems, and that's why you don't need to run fsck on them. You don't need to write the journal synchronously, you can do these things in groups. The softupdates mechanism does something similar; only it doesn't maintain an on-disk journal, and hence needs fsck after boot to fix up the free block bitmaps and stuff (basically performing a garbage collection on the filesystem, which, unfortunately, is pretty slow). mkb.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200506171620.j5HGKxwW042819>