Date: Thu, 28 Apr 2011 09:26:01 GMT From: Helmut Schneider <jumper99@gmx.de> To: freebsd-gnats-submit@FreeBSD.org Subject: kern/156691: panic when using hard disks as RAW devices within VMWare ESXi 4.1-u1 Message-ID: <201104280926.p3S9Q17j084801@red.freebsd.org> Resent-Message-ID: <201104280930.p3S9UCnT080203@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 156691 >Category: kern >Synopsis: panic when using hard disks as RAW devices within VMWare ESXi 4.1-u1 >Confidential: no >Severity: critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Apr 28 09:30:12 UTC 2011 >Closed-Date: >Last-Modified: >Originator: Helmut Schneider >Release: 8.2-RELEASE-p1 >Organization: >Environment: >Description: Within VMWare ESXi 4.1-u1 I created RAW devices using http://www.mattiasholm.com/node/33. When I install FreeBSD the filesystem gets corrupted (IIRC during the installation "ELF interpreter /libexec/ld-elf.so.1 not found " pops up many times). Also, when I copy a large number of files or directories to the devices (tried cp, dump/restore and rsync) the VM panics immediately. Unfortunately /var/crash remains empty after reboot. If there is another way to create a backtrace please advice. Disks are 2 seagate 80GB SATA and one seagate 400GB SATA-II Using FreeBSD 8.x I can - partition and label the disks - copy a few files to it, create a few directories on it I tested the following OSses within the same VM using the same RAW devices and they install and operate fine: Windows 7 Ubuntu 10.4 OpenBSD 4.8 The disks were all tested with seatools which reported no errors. I can also install and use the disks without problems on a physical machine. After the crash/panic most of the time the data on the first MBR-UFS partition (and only the first partition!) is complete rubbish, after fsck only a few files within lost+found remain. Sometimes also all labels are gone but are easily restoreable using bsdlabel -R. The problem is easily reproducable (here). I tried with open-vm-tools-nox11-313025_2 and without, also booting mfsbsd and then copy files. >How-To-Repeat: Run ESXi 4.1-u1 Create RAW devices according to http://www.mattiasholm.com/node/33 Install FreeBSD on it >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201104280926.p3S9Q17j084801>