Received: by 2002:a25:c205:0:0:0:0:0 with SMTP id s5csp6876052ybf; Fri, 6 Mar 2020 06:15:52 -0800 (PST) X-Google-Smtp-Source: ADFU+vv3UtCp86oHlGqR4YtyaAWTDijj+/8LJ1DkyJ6M+AL2vcIbFz0SW63QGF0ib+tu+h8eDqdU X-Received: by 2002:aca:57d6:: with SMTP id l205mr2682390oib.20.1583504152098; Fri, 06 Mar 2020 06:15:52 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1583504152; cv=none; d=google.com; s=arc-20160816; b=qDU+/z/JqWGPaUebd9Nehw3MaPWhldsqojFg+GlbWb6CzD/owL4P4pg3w674zOtobx 6+2j1Lo/1BjqEESxfkoCxq56OmW8SfHyWItbk8PPHFVK6HFR4SSlIHqytwD60COyhmnG t0+MkhEzhl7mzsyiduIcOh3uLKTiOm7JHhhoOuUAbd2oM+ZS7vcOKjESePeaBNpGNAtd VJYf7IiTIMzH0zHrBJHAgYbTd1q7zDcPByYpv74RK4ncYlJNUJ0tZdCC4I9NpRrM54Lx /VnCIHIzVRw9PSdzrYSkV3gHA9/F2aoPLWZ6E7txDiUwUED8hEBvhGQScIxMQOsjUkWC zA5A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=1Cxlwvc8fdeo8u+MHJZX2s5BT2d6dpWKDzLqXVKseCA=; b=Dmrt2FRMKex5cLFytHem8NW7e1JIRgybpeZV6BQT++Xamezrd0VYpxOhYttIT6FqI1 zrPG7SIdav1ilXLtwi3XHru8vwtruAG7/GgxPWOMpKAwfEEPEUHumjUS4f4lXvGmrmM7 12bJBvIP14jOiOJtxd4cB58X81OzpfK7TY4vWkExNfUmpFTSJk6msbzUXaS6EzvPvO6d 2xhKZ359UfqQ74KpaL16IwUigF6FEZRsgj4ytRGLAiEIXT06TVCl3fvTV3+eCz8sAqB/ z3Z9Gd1Un6nE3Wf44aM+4Q9FI9gxIzHeoii8YNSygNqnugGbUTlNSXrNRrTDViqGmvv2 4zWA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-ext4-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-ext4-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id y13si1459263oto.33.2020.03.06.06.15.32; Fri, 06 Mar 2020 06:15:52 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-ext4-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-ext4-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-ext4-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726194AbgCFOP1 (ORCPT + 99 others); Fri, 6 Mar 2020 09:15:27 -0500 Received: from outgoing-auth-1.mit.edu ([18.9.28.11]:37369 "EHLO outgoing.mit.edu" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726368AbgCFOP1 (ORCPT ); Fri, 6 Mar 2020 09:15:27 -0500 Received: from callcc.thunk.org (pool-72-93-95-157.bstnma.fios.verizon.net [72.93.95.157]) (authenticated bits=0) (User authenticated as tytso@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 026EFN8K004649 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 6 Mar 2020 09:15:23 -0500 Received: by callcc.thunk.org (Postfix, from userid 15806) id 1762942045B; Fri, 6 Mar 2020 09:15:23 -0500 (EST) Date: Fri, 6 Mar 2020 09:15:23 -0500 From: "Theodore Y. Ts'o" To: Alok Jain Cc: linux-ext4@vger.kernel.org, Andreas Dilger Subject: Re: Ext4 errors in linux /var/log/messages Message-ID: <20200306141523.GA121760@mit.edu> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-ext4-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-ext4@vger.kernel.org On Fri, Mar 06, 2020 at 07:29:22PM +0530, Alok Jain wrote: > Hi Guys, > > Thanks for providing the forum to check the issue, I already got > really helpful responses and need one more help wrt to EXT4 log > messages coming in /var/log/messages file > > 1) I have iSCSI device attached to my VM > 2) Copied and extracted files in the attached device > 3) Unmount and disconnected the device, post disconnect operation I > can see lots of EXT4 file system errors in /var/log/messages file, > attaching the same (err.txt) for review. > > I am not sure what these log messages are correspond to as the device > was already disconnected at Feb I1:22:42, but th*e ext4 log messages > came after that, can you please review and share your findings. There's nothing really deep here. Ext4 wasn't able to write to /dev/sdd1. Assuming that /dev/sdd is your iSCSI device, it's probably because the connection to the iSCSI device had gotten disrupted. This is similar to what you might see if you were writing to a USB thumbstick and the USB device is unceremoniously yanked out. One possible scenario is thar while the umount was *started*, but it had not completed writing out dirty blocks before the iSCSI device was disconnected. If that's true, this would be a case of operator error. - Ted