From: Eric Sandeen Subject: Re: Difference in jbd2 behavior between CentOS and Ubuntu while unmounting Date: Tue, 17 May 2016 21:41:07 -0500 Message-ID: <782fe069-c14f-4bae-609e-bbad554cb657@redhat.com> References: <32a9cbf4-4e2d-335c-0603-9639b30e2863@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: linux-ext4@vger.kernel.org To: Kamran Khan Return-path: Received: from mx1.redhat.com ([209.132.183.28]:45128 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752366AbcERClK (ORCPT ); Tue, 17 May 2016 22:41:10 -0400 In-Reply-To: Sender: linux-ext4-owner@vger.kernel.org List-ID: On 5/17/16 9:35 PM, Kamran Khan wrote: > Yup, the kernel versions are drastically different. It's 3.10 vs 4.2. > > The problem on 3.10 though is, while jbd2 holds on to the unmounted > device I cannot even rmmod jbd2 or ext4 *even if no other ext > filesystems are mounted*. That lock makes it all but impossible to do > anything with the block device. You may as well try Centos7.2, at least, there are 50+ updates to jbd2 & ext4 since 7.1. If it still persists we can dig further. -Eric > On Tue, May 17, 2016 at 7:17 PM, Eric Sandeen wrote: >> On 5/17/16 7:46 PM, Kamran Khan wrote: >>> I'm trying to understand the difference in jbd2 behavior across Ubuntu >>> 14.04 and Centos 7.1. Will appreciate any help. >> >> For starters, what kernel versions are those? (I know what centos >> is, "3.10.0" with updates, which I can check out, but I have no idea >> what might be in the Ubuntu distro) >> >> -Eric > > >