Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261524AbUCVA7z (ORCPT ); Sun, 21 Mar 2004 19:59:55 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261602AbUCVA7z (ORCPT ); Sun, 21 Mar 2004 19:59:55 -0500 Received: from uslink-66.173.43-133.uslink.net ([66.173.43.133]:33928 "EHLO dingdong.cryptoapps.com") by vger.kernel.org with ESMTP id S261524AbUCVA7z (ORCPT ); Sun, 21 Mar 2004 19:59:55 -0500 Date: Sun, 21 Mar 2004 16:59:54 -0800 From: Chris Wedgwood To: Pascal Schmidt Cc: Frank Cusack , linux-kernel@vger.kernel.org Subject: Re: Does Linux sync(2) wait? Message-ID: <20040322005953.GA12237@dingdong.cryptoapps.com> References: <1C8xa-5lk-5@gated-at.bofh.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 571 Lines: 15 On Sun, Mar 21, 2004 at 04:30:53PM +0100, Pascal Schmidt wrote: > No idea about NFS, but sync(1) does wait. When I push 500M out to my > MO drive, the cp operation returns fairly quickly because I usually > have more than 500M free memory. Then I run sync(1), which takes > about 20 minutes before it returns. 20 minutes?! - 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/