Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 14 Oct 2003 06:59:29 -0700 (PDT) Received: from imag.imag.fr (imag.imag.fr [129.88.30.1]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h9EDwm25029712 for ; Tue, 14 Oct 2003 06:58:50 -0700 Received: from mail-veri.imag.fr (pave.imag.fr [129.88.43.12]) by imag.imag.fr (8.12.10/8.12.10) with ESMTP id h9EDwjd8025354 for ; Tue, 14 Oct 2003 15:58:45 +0200 (CEST) Received: from astazou.imag.fr ([129.88.43.102] helo=astazou.imag.fr.imag.fr ident=kowalski) by mail-veri.imag.fr with esmtp (Exim 3.35 #1 (Debian)) id 1A9PhF-0005Ox-00 for ; Tue, 14 Oct 2003 15:58:45 +0200 To: linux-xfs@oss.sgi.com Subject: XFS and async NFS exports From: Nicolas Kowalski Mail-Copies-To: never Date: Tue, 14 Oct 2003 15:58:43 +0200 Message-ID: User-Agent: Gnus/5.1002 (Gnus v5.10.2) XEmacs/21.4 (Common Lisp, linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-IMAG-MailScanner: Found to be clean X-IMAG-MailScanner-Information: Please contact the ISP for more information X-archive-position: 713 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: Nicolas.Kowalski@imag.fr Precedence: bulk X-list: linux-xfs Content-Length: 688 Lines: 22 Hello. [I apologize, this is not completely XFS-related, but perhaps some XFS+NFS gurus will be able to give some information.] I recently faced a power outage on a fileserver with XFS filesystems (CVS-2003-09-24_05). Some files written on NFS clients a few seconds before the crash were damaged (zero-sized). On a first approach, I thought this was XFS-related, but afterwards, I also realized that this server was exporting its filesystems with the async export option...It this possible that this async option have caused these file damages ? If I use sync exports, does this mean that XFS will effectively write on disk all pending data ? Many thanks in advance. -- Nicolas