From owner-freebsd-emulation@FreeBSD.ORG Sun May 22 16:13:06 2011 Return-Path: Delivered-To: freebsd-emulation@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A21D91065677 for ; Sun, 22 May 2011 16:13:06 +0000 (UTC) (envelope-from jumper99@gmx.de) Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by mx1.freebsd.org (Postfix) with SMTP id 14FD08FC12 for ; Sun, 22 May 2011 16:13:05 +0000 (UTC) Received: (qmail invoked by alias); 22 May 2011 16:13:04 -0000 Received: from p5DCD73B0.dip.t-dialin.net (EHLO ORPHEUS) [93.205.115.176] by mail.gmx.net (mp043) with SMTP; 22 May 2011 18:13:04 +0200 X-Authenticated: #682707 X-Provags-ID: V01U2FsdGVkX18bY1pFLyEbm3Zn+N5dx6sGckh4VHQ83YiqZgaO32 vf8XtO/SmseMWd Message-ID: <2B234D3675644859B3C3241CDE7FD0AB@charlieroot.de> From: "Helmut Schneider" To: Date: Sun, 22 May 2011 18:13:04 +0200 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 14.0.8117.416 X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8117.416 X-Antivirus: avast! (VPS 110522-0, 22.05.2011), Outbound message X-Antivirus-Status: Clean X-Y-GMX-Trusted: 0 Cc: jh@FreeBSD.org, freebsd-emulation@FreeBSD.org Subject: Re: kern/156691: [vmware] [panic] panic when using hard disks as RAW devices within VMWare ESXi 4.1-u1 X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 May 2011 16:13:06 -0000 Appendix: I tried with BusLogic Parallel (FreeBSD-32bit), LSI Logic Parallel and LSI Logic SAS (both FreeBSD-64bit). The problem remains (I hope that was what you ment with "try using a different storage controller"). But what is interesting (and makes me think that the controller is not to blame): I re-partition the disk using gpart: mfsbsd# gpart show da1 => 34 156301421 da1 GPT (75G) 34 128 1 freebsd-boot (64K) 162 4194304 2 freebsd-ufs (2.0G) 4194466 4194304 3 freebsd-swap (2.0G) 8388770 20971520 4 freebsd-ufs (10G) 29360290 4194304 5 freebsd-ufs (2.0G) 33554594 4194304 6 freebsd-ufs (2.0G) 37748898 2097152 7 freebsd-ufs (1.0G) 39846050 4194304 8 freebsd-ufs (2.0G) 44040354 4194304 9 freebsd-ufs (2.0G) 48234658 8388608 10 freebsd-ufs (4.0G) 56623266 16777216 11 freebsd-ufs (8.0G) 73400482 8388608 12 freebsd-ufs (4.0G) 81789090 62914560 13 freebsd-ufs (30G) 144703650 4194304 14 freebsd-ufs (2.0G) 148897954 7403501 15 freebsd-ufs (3.5G) mfsbsd# I now copy ~30GB of data (actually a clone of a running system using vdisks) to those partitons except for the designated / partition (da1p2). The system does *not* panic. (I used rsync to push the data from the live system if it is worth to mention it) mfsbsd# df -h | grep da1 /dev/da1p2 1.9G 12K 1.8G 0% /mnt/da1 /dev/da1p4 9.7G 5.5G 3.4G 62% /mnt/da1/usr /dev/da1p5 1.9G 290M 1.5G 16% /mnt/da1/var /dev/da1p6 1.9G 804M 1.0G 44% /mnt/da1/var/log /dev/da1p7 989M 143M 767M 16% /mnt/da1/var/amavis /dev/da1p8 1.9G 998K 1.8G 0% /mnt/da1/var/spool /dev/da1p9 1.9G 5.8M 1.8G 0% /mnt/da1/var/named /dev/da1p10 3.9G 989M 2.6G 27% /mnt/da1/var/squid /dev/da1p11 7.7G 1.9G 5.3G 26% /mnt/da1/var/www /dev/da1p12 3.9G 1.3G 2.3G 35% /mnt/da1/var/db/mysql /dev/da1p13 29G 18G 8.7G 67% /mnt/da1/var/vsftpd /dev/da1p14 1.9G 118K 1.8G 0% /mnt/da1/tmp /dev/da1p15 3.4G 31M 3.1G 1% /mnt/da1/home mfsbsd# But as soon as I rsync/dump/cp the / partition the panic occurs. Reliable.