From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cuda.sgi.com (cuda3.sgi.com [192.48.176.15]) by oss.sgi.com (8.14.3/8.14.3/SuSE Linux 0.8) with ESMTP id n4K6wTA9095330 for ; Wed, 20 May 2009 01:58:30 -0500 Received: from kcout02.prserv.net (localhost [127.0.0.1]) by cuda.sgi.com (Spam Firewall) with ESMTP id 3672A19EED77 for ; Tue, 19 May 2009 23:58:38 -0700 (PDT) Received: from kcout02.prserv.net (kcout02.prserv.net [12.154.55.32]) by cuda.sgi.com with ESMTP id tSLC7D6IPoRE6iuX for ; Tue, 19 May 2009 23:58:38 -0700 (PDT) Message-ID: <4A13AA1B.7080801@attglobal.net> Date: Tue, 19 May 2009 23:58:35 -0700 From: Eddie Atherton MIME-Version: 1.0 Subject: XFS internal error xfs_trans_cancel at line 1164 of file fs/xfs/xfs_trans.c Reply-To: stunnel@attglobal.net List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xfs-bounces@oss.sgi.com Errors-To: xfs-bounces@oss.sgi.com To: xfs@oss.sgi.com I'm trying to install a clean Slackware 12.2 (2.6.27.7) under ESXi, and can almost guarantee getting this error immediately after formatting the root partition. It's happened 4 out of the 5 times I've tried, so far. The sequence of commands, after digging through the install scripts, that lead to this failure are just: mkfs.xfs mount mkdir Apologies for posting the stack trace as a couple of jpg's, but it's the only way I could capture them, as I don't have any VMs set up, yet, that have conectivity to upload any files. The stack trace can be found at: http://www.bogolinux.net/xfs_crash_a.JPG http://www.bogolinux.net/xfs_crash_b.JPG I'm guessing that it's something to do with this running under a VM, but is there any way to stop it happening. Cheers, Eddie _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs