From owner-freebsd-fs@freebsd.org Wed Nov 8 09:04:48 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5B4E7E71D45 for ; Wed, 8 Nov 2017 09:04:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0F0FF713FB for ; Wed, 8 Nov 2017 09:04:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id vA894lsI005868 for ; Wed, 8 Nov 2017 09:04:47 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 223491] fsck_ufs: Directory XXXX name not found Date: Wed, 08 Nov 2017 09:04:48 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: wosch@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Nov 2017 09:04:48 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223491 --- Comment #2 from Wolfram Schneider --- It is an Intel 64bit CPU with a shared SSD. I guess the data center is using QEMU/KVM for the virtualization, but I=E2=80=99m not sure about that. $ df -h Filesystem Size Used Avail Capacity Mounted on /dev/vtbd0p2 93G 63G 23G 73% / devfs 1.0K 1.0K 0B 100% /dev sysctl -a kern.geom.label.disk_ident.enable: 1 kern.geom.disk.cd0.flags: 0 kern.geom.disk.cd0.led:=20 kern.geom.disk.vtbd0.flags: 3a kern.geom.disk.vtbd0.led:=20 kern.disks: cd0 vtbd0 SSD write performance ca: 140Mbyte/s=20 SSD read performance ca: 560Mbyte/s FreeBSD 12.0-CURRENT #0 fcca5326804(master): Mon Oct 23 13:24:36 CEST 2017 root@freebsd:/usr/obj/usr/src/sys/GENERIC-NODEBUG amd64 FreeBSD clang version 5.0.0 (tags/RELEASE_500/final 312559) (based on LLVM 5.0.0svn) CPU: Intel(R) Xeon(R) CPU E5-2630 v4 @ 2.20GHz (2200.05-MHz K8-class CPU) real memory =3D 8589934592 (8192 MB) FreeBSD/SMP: Multiprocessor System Detected: 6 CPUs virtio_pci0: port 0xc080-0xc0bf mem 0xf2060000-0xf2060fff irq 11 at device 4.0 on pci0 vtblk0: on virtio_pci0 vtblk0: 102400MB (209715200 512 byte sectors) virtio_pci1: port 0xc0c0-0xc0df irq 10 at devi= ce 5.0 on pci0 vtballoon0: on virtio_pci1 ugen0.2: at usbus0 Trying to mount root from ufs:/dev/vtbd0p2 [rw]... --=20 You are receiving this mail because: You are the assignee for the bug.=