Received: by 2002:a05:6a10:af89:0:0:0:0 with SMTP id iu9csp2379096pxb; Sun, 16 Jan 2022 18:54:10 -0800 (PST) X-Google-Smtp-Source: ABdhPJw35g7gGMOOdzcG5VNC1ORlOo9EpQ5PUKKM1r/GHVLb4kASaGkgFBNTnfn1A/MejUATImSG X-Received: by 2002:a17:90b:384d:: with SMTP id nl13mr22859611pjb.46.1642388049919; Sun, 16 Jan 2022 18:54:09 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1642388049; cv=none; d=google.com; s=arc-20160816; b=fmntw5Lru2JNlHjAbVx+wQLFyNb8JPrMWkWtEfd3hoJDxmOGsd6yAbKGh+hwWUIVCO kzIOASkKuhu3nYyCbwZpKw3lbz9FZcYkBLPVBFho3UKVMueFFlhlwizwd9xWn3Z9jELn jCgfP4tXh1JujBSAjPN227aEAmNXDmnZiyHWeEMpZy062A/XxIkf2dySPxlvmM8nHxng mQ6Hv0debq0OoVJJrGHrYQVhg4pgeGlkEDNBQ5fZYWS0XiArEIHc0zopSQD3eCPSEzsm 0bK1x2kgqStbfDq8tyginvRhg7VyVUeTo+NQ1p23170S5Qi0WQ8ssCkhnDoRAm/830Pa EmoA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language:to :subject:from:user-agent:mime-version:date:message-id; bh=DNP8eu2Ok4YmCxjK+UgiIcv0q82ZYjCDxfNmN9CWIuM=; b=aQvXwKefD8hRNB8WEvdPRsC4aTls4A5+/5P5z4MvvQkFSWrsGf80RrGoYcPK0KHL+J +kVWuvoy5D4FHZHSQfni/SoxsxL1HG3WjrqgLdivXMUaBc1eoQwQPuuiBmfuqoj4uXEW NZP8F2moMFJ3OLCipb75nHCFyc0/h9KafAjhkRxPBD8HZRPd4r7uA7mueTbAYDj56TGu JZ1OeurqjUvRsDvZ0wgJDQ3YacZ3BCbfM3FjeXvsY0BQBWdR7Gg+TPVdh0F5cdjpmr2a oC7Rh+5t9uVJIGTwzlCXmSdWvFbh66OiP5VrHhECw+/ptunQyDzceaOkvTV0QtCwjr5m O11Q== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=memeplex.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id d20si12209742pls.220.2022.01.16.18.53.57; Sun, 16 Jan 2022 18:54:09 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=memeplex.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234096AbiAPCFY (ORCPT + 99 others); Sat, 15 Jan 2022 21:05:24 -0500 Received: from inbound.memeplex.com ([35.162.238.239]:53876 "EHLO relay.memeplex.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S234072AbiAPCFX (ORCPT ); Sat, 15 Jan 2022 21:05:23 -0500 Received: from mail.memeplex.com ([35.162.238.239]) by relay.memeplex.com (Postfix) with ESMTPS id 6B73F4012F for ; Sun, 16 Jan 2022 02:05:23 +0000 (UTC) Message-ID: Date: Sat, 15 Jan 2022 18:05:22 -0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.5.0 From: Andrew than Subject: Catastrophic data loss in Mac OS X VirtualBox guest running Linux ubuntu 5.11.0-41-generic To: linux-kernel@vger.kernel.org Content-Language: en-US Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Please cc: me on any response, I am not subscribed to LKML I've posted this issue on the Virtual Box bug reporting site at Oracle, but I'm not sure whether it's a VirtualBox only issue. Would someone please direct me as to how best to pursue this issue with the kernel gods? It's not clear to me that the problem is in a storage driver because I was also getting soft lockup errors reported prior to the data loss. [1359528.850122] systemd-journald[284]: Failed to write entry (22 items, 739 bytes), ignoring: Read-only file system (the above dmesg reported error occurs many many times with different timestamps of course) which seems to stem from: Jan 15 21:35:14 ubuntu CRON[1188952]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Jan 15 21:37:35 ubuntu kernel: [1355482.810724] ata3.00: exception Emask 0x0 SAct 0x8000000 SErr 0x0 action 0x6 frozen Jan 15 21:37:35 ubuntu kernel: [1355482.810769] ata3.00: failed command: WRITE FPDMA QUEUED Jan 15 21:37:35 ubuntu kernel: [1355482.810786] ata3.00: cmd 61/10:d8:90:a0:53/00:00:00:00:00/40 tag 27 ncq dma 8192 out Jan 15 21:37:35 ubuntu kernel: [1355482.810786] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 15 21:37:35 ubuntu kernel: [1355482.810824] ata3.00: status: { DRDY } Jan 15 21:37:35 ubuntu kernel: [1355482.810839] ata3: hard resetting link Jan 15 21:37:37 ubuntu kernel: [1355485.044289] ata3: SATA link down (SStatus 1 SControl 300) Jan 15 21:37:42 ubuntu kernel: [1355490.294132] ata3: hard resetting link Jan 15 21:37:45 ubuntu kernel: [1355492.509352] ata3: SATA link down (SStatus 1 SControl 300) Jan 15 21:38:07 ubuntu kernel: [1355497.707142] ata3: hard resetting link Sorry about the formatting of these ... although looking at this again, maybe it *is* an issue with the SATA drivers that affects any system that writes to disk?? [483574.483756] watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [swapper/1:0] Jan 6 11:36:36 ubuntu kernel: [541789.358312] watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [swapper/1:0] Jan 6 13:37:15 ubuntu kernel: [549027.924906] watchdog: BUG: soft lockup - CPU#1 stuck for 21s! [swapper/1:0] Jan 6 13:37:15 ubuntu kernel: [549027.925052] do_softirq+0xce/0x281 Jan 6 13:37:15 ubuntu kernel: [549027.925059] do_softirq_own_stack+0x3d/0x50 Jan 7 05:12:07 ubuntu kernel: [605122.533658] watchdog: BUG: soft lockup - CPU#1 stuck for 21s! [swapper/1:0]