From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.wl.linuxfoundation.org ([198.145.29.98]:38222 "EHLO mail.wl.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725790AbeLCDvW (ORCPT ); Sun, 2 Dec 2018 22:51:22 -0500 Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id 6DD012AA0D for ; Mon, 3 Dec 2018 03:51:18 +0000 (UTC) From: bugzilla-daemon@bugzilla.kernel.org To: linux-ext4@vger.kernel.org Subject: [Bug 201685] ext4 file system corruption Date: Mon, 03 Dec 2018 03:51:16 +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 #187 from Eric Benoit (eric@ecks.ca) --- (In reply to Theodore Tso from comment #183) > Eric, re #180, could you upload your .config file for your kernel and the > boot-command line? I'm interested in particular what I/O scheduler you are > using. And are you using the same .config and boot command line (and other > system configurations) on your other system where you were seeing the > problem? Many thanks!! [ 0.000000] Command line: BOOT_IMAGE=/root@/boot/vmlinuz root=simcoe/root triggers=zfs radeon.dpm=1 # cat /sys/block/sd[a-d]/queue/scheduler [none] [none] [none] [none] The config between 4.18.20 and 4.19.6 are about as identical as possible, the only differences being whatever was added in 4.19 and prompted by make oldconfig. Between this machine and the other (a server) the only differences would be in specific hardware support and options suitable for that application. In terms of schedulers, block devices, and filesystem support, they're the same. -- You are receiving this mail because: You are watching the assignee of the bug.