From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.wl.linuxfoundation.org ([198.145.29.98]:55348 "EHLO mail.wl.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725856AbeLBOV0 (ORCPT ); Sun, 2 Dec 2018 09:21:26 -0500 Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id BD0982AA26 for ; Sun, 2 Dec 2018 14:21:23 +0000 (UTC) From: bugzilla-daemon@bugzilla.kernel.org To: linux-ext4@vger.kernel.org Subject: [Bug 201685] ext4 file system corruption Date: Sun, 02 Dec 2018 14:21:22 +0000 Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 Sender: linux-ext4-owner@vger.kernel.org List-ID: https://bugzilla.kernel.org/show_bug.cgi?id=201685 --- Comment #147 from Rainer Fiebig (jrf@mailbox.org) --- (In reply to Reindl Harald from comment #131) > has anybody ever seen that bug within a virtual machine? > > i currently run 4.19.x only inside VMs on VMware Workstation / VMware ESXi > and did not see any issues, my only phyiscal test was my homeserver which > completley crahsed 4 times like because of the VMware Workstation 14 > kernel-modules lasted only for a weekend (RAID10, 2 Samsung Evo 850 2 TB, 2 > Samsung Evo 860 2 TB) after the last crash left a 0 byte "firewall.sh" in > the nested VM i was working for hours I've installed 4.19.x with a defconfig in a VirtualBox-VM, hoping the issue would show up and I could bisect it there. I've also varied the config-params that have been discussed here. But unfortunately that damn thing runs as nicely in the VM as it does on real iron - at least here. :) -- You are receiving this mail because: You are watching the assignee of the bug.