From: Eric Sandeen <sandeen@redhat.com>
To: Kamran Khan <krkhan@inspirated.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Difference in jbd2 behavior between CentOS and Ubuntu while unmounting
Date: Tue, 17 May 2016 21:41:07 -0500 [thread overview]
Message-ID: <782fe069-c14f-4bae-609e-bbad554cb657@redhat.com> (raw)
In-Reply-To: <CAN0j2-cp1odcT44ZoeFDGHMF519F2b9Ffa5vc8PJyJfSLcj5-Q@mail.gmail.com>
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 <sandeen@redhat.com> 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
>
>
>
next prev parent reply other threads:[~2016-05-18 2:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 0:46 Difference in jbd2 behavior between CentOS and Ubuntu while unmounting Kamran Khan
2016-05-18 1:33 ` Kamran Khan
2016-05-18 2:14 ` Kamran Khan
2016-05-18 2:17 ` Eric Sandeen
2016-05-18 2:35 ` Kamran Khan
2016-05-18 2:41 ` Eric Sandeen [this message]
2016-05-18 2:55 ` Kamran Khan
2016-05-18 3:16 ` Eric Sandeen
2016-05-18 3:22 ` Kamran Khan
2016-05-18 6:18 ` Darrick J. Wong
2016-05-18 14:12 ` Theodore Ts'o
2016-05-18 19:01 ` Kamran Khan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=782fe069-c14f-4bae-609e-bbad554cb657@redhat.com \
--to=sandeen@redhat.com \
--cc=krkhan@inspirated.com \
--cc=linux-ext4@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox