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] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 18 May 2016 10:12:40 -0400
From:	Theodore Ts'o <tytso@....edu>
To:	"Darrick J. Wong" <darrick.wong@...cle.com>
Cc:	Eric Sandeen <sandeen@...hat.com>,
	Kamran Khan <krkhan@...pirated.com>, linux-ext4@...r.kernel.org
Subject: Re: Difference in jbd2 behavior between CentOS and Ubuntu while
 unmounting

On Tue, May 17, 2016 at 11:18:34PM -0700, Darrick J. Wong wrote:
> Just to throw some gasoline on this fire, I hit the same set of symptoms
> a couple of weeks ago while trying to umount /home on 4.5.0 + Ubuntu 16.04.
> Ted mused that it could be some process running in a funny mount namespace.
> Or systemd dragons.  Or something.

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.)

Another simple thing to try doing is to go into single user mode,
which will kill off all/most of your userspace processes, which may
also have the desired effect.  Much more of a blunt hammer, though.

     	      	      	       	    	 - Ted
--
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