Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 16 Feb 2004 08:50:00 -0800 (PST) Received: from medoc.inf.ethz.ch (medoc.inf.ethz.ch [129.132.178.200]) by oss.sgi.com (8.12.10/8.12.9) with SMTP id i1GGnZKO012255 for ; Mon, 16 Feb 2004 08:49:35 -0800 Received: from localhost (localhost [127.0.0.1]) by medoc.inf.ethz.ch (Postfix) with ESMTP id B6504DB3F; Mon, 16 Feb 2004 17:21:16 +0100 (MET) Received: from medoc.inf.ethz.ch ([127.0.0.1]) by localhost (medoc [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 22263-01-3; Mon, 16 Feb 2004 17:21:16 +0100 (MET) Received: by medoc.inf.ethz.ch (Postfix, from userid 42460) id 6D2C6DB3E; Mon, 16 Feb 2004 17:21:16 +0100 (MET) Received: from 129.132.10.58 (SquirrelMail authenticated user mschmitt) by www.mail.inf.ethz.ch with HTTP; Mon, 16 Feb 2004 17:21:15 +0100 (MET) Message-ID: <32995.129.132.10.58.1076948475.squirrel@www.mail.inf.ethz.ch> In-Reply-To: <32871.129.132.10.58.1076945932.squirrel@www.mail.inf.ethz.ch> References: <1076941244.4030d1bc0eb22@www.mail.inf.ethz.ch> <32871.129.132.10.58.1076945932.squirrel@www.mail.inf.ethz.ch> Date: Mon, 16 Feb 2004 17:21:15 +0100 (MET) Subject: Re: XFS: Filesystem sd(8,50) has duplicate UUID - can't mount From: mschmitt@inf.ethz.ch To: mschmitt@inf.ethz.ch Cc: linux-xfs@oss.sgi.com User-Agent: SquirrelMail/1.4.2 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 X-Priority: 3 Importance: Normal X-Virus-Scanned: by amavisd-new at inf.ethz.ch Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id i1GGnkKO012256 X-archive-position: 2105 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: mschmitt@inf.ethz.ch Precedence: bulk X-list: linux-xfs Well, the xfs_repair did not fix the problem. I'm running NFS/SMB now on the fs mounted with -nouuid, I hope that's not a problem... Will the error message in the subject go away with a reboot only? Greetz Marc > Any idea how to find out what could have been the problem? The xfs_repair > (xfsprogs-2.6.2-0_7.rh7.3.at) is still running and will continue doing so > for a while, I guess...