linux-ext4 - Re: Difference in jbd2 behavior between CentOS and Ubuntu while unmounting

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAN0j2-duVA45Vr40rza-PLcwhx6z+KHAGT9Wj+dCGWwwmp9qdQ@mail.gmail.com>
Date:	Wed, 18 May 2016 12:01:43 -0700
From:	Kamran Khan <krkhan@...pirated.com>
To:	"Theodore Ts'o" <tytso@....edu>
Cc:	"Darrick J. Wong" <darrick.wong@...cle.com>,
	Eric Sandeen <sandeen@...hat.com>, linux-ext4@...r.kernel.org
Subject: Re: Difference in jbd2 behavior between CentOS and Ubuntu while unmounting

On Wed, May 18, 2016 at 7:12 AM, Theodore Ts'o <tytso@....edu> wrote:
> Try the following to see if someone process is playing namespace games
>
> find /proc -name mounts | xargs grep /dev/sda3
>
> (replace /dev/sda3 with the device that you think is unmounted).
>
> When you find the process, kill it.  (Or try doing a service XXX
> restart assuming that the device has been unmounted in the "normal"
> mount namespace.)

That did the trick! systemd-udevd was the culprit. Somehow it wasn't
appearing in lsof/fuser outputs but had the block device listed in its
mounts.

Killed it and the block device was released for further operations.

Thanks!!
-- 
Kamran.

http://inspirated.com/
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html