Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261297AbVD0JO0 (ORCPT ); Wed, 27 Apr 2005 05:14:26 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261299AbVD0JO0 (ORCPT ); Wed, 27 Apr 2005 05:14:26 -0400 Received: from hermine.aitel.hist.no ([158.38.50.15]:9993 "HELO hermine.aitel.hist.no") by vger.kernel.org with SMTP id S261297AbVD0JOX (ORCPT ); Wed, 27 Apr 2005 05:14:23 -0400 Message-ID: <426F5902.6060901@aitel.hist.no> Date: Wed, 27 Apr 2005 11:18:58 +0200 From: Helge Hafting User-Agent: Debian Thunderbird 1.0 (X11/20050116) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kyle Moffett CC: Xin Zhao , linux-kernel@vger.kernel.org Subject: Re: Ext3+ramdisk journaling problem References: <4ae3c14050424182235f916d7@mail.gmail.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1079 Lines: 28 Kyle Moffett wrote: > On Apr 24, 2005, at 21:22, Xin Zhao wrote: > >> hi, >> >> I used ramdisk as an ext3 journal and mount ext3 file system with >> option data=journal. It worked fine and speedup the ext3 file system. > > > Uhh, the whole point of a journal is that when the computer goes down > hard and doesn't have a chance to clean up. If you put the journal on > a ramdisk, you might as well just mount it as an ext2 filesystem and > be done with it. Without the journal _on_disk_ you get no data or > filesystem reliability advantages. If you're after speed, just forgo > the reliability or buy better disks. > Alternative: Buy a real ramdisk with battery-backup instead of using a "ramdisk" in system ram. Such a thing will last across a reboot, offering both nice speed and all the comforts of a journal. Helge Hafting - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/