Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261804AbVCAIr6 (ORCPT ); Tue, 1 Mar 2005 03:47:58 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261767AbVCAIr6 (ORCPT ); Tue, 1 Mar 2005 03:47:58 -0500 Received: from ns.virtualhost.dk ([195.184.98.160]:30672 "EHLO virtualhost.dk") by vger.kernel.org with ESMTP id S261804AbVCAIrv (ORCPT ); Tue, 1 Mar 2005 03:47:51 -0500 Date: Tue, 1 Mar 2005 09:47:42 +0100 From: Jens Axboe To: Greg Stark Cc: Linux Kernel , Bartlomiej Zolnierkiewicz , Jeff Garzik , linux-scsi@vger.kernel.org Subject: Re: [PATCH] scsi/sata write barrier support Message-ID: <20050301084741.GD12295@suse.de> References: <20050127120244.GO2751@suse.de> <87acpxurwf.fsf@stark.xeocode.com> <20050222071340.GC2835@suse.de> <874qg4v81q.fsf@stark.xeocode.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <874qg4v81q.fsf@stark.xeocode.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 794 Lines: 25 On Tue, Feb 22 2005, Greg Stark wrote: > > Jens Axboe writes: > > > fsync has been working all along, since the initial barrier support for > > ide. only ext3 and reiserfs support it. > > Really? That's huge news. Since what kernel version(s) is that? Since 2.6.9. > What about a non-journaled fs, or at least a meta-data-only-journaled fs? > Journaled FS's don't mix well with transaction based databases since they're > basically doing their own journaling anyways. Only works on ext3 and reiserfs currently. -- Jens Axboe - 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/