From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751919AbdEDVOH (ORCPT ); Thu, 4 May 2017 17:14:07 -0400 Received: from shells.gnugeneration.com ([66.240.222.126]:37140 "EHLO shells.gnugeneration.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751158AbdEDVOG (ORCPT ); Thu, 4 May 2017 17:14:06 -0400 X-Greylist: delayed 599 seconds by postgrey-1.27 at vger.kernel.org; Thu, 04 May 2017 17:14:06 EDT Date: Thu, 4 May 2017 14:06:26 -0700 From: vcaputo@pengaru.com To: linux-kernel Subject: [REGRESSION] 4.11.0-rc8 ext4 mount randomly returning EBUSY during boot w/systemd? Message-ID: <20170504210626.GN25821@shells.gnugeneration.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org I'm not sure about this one, but never experienced it prior to 4.11.0-rc8. During boot sometimes the home.mount unit fails and `systemctl status home.mount` reports that the mount failed due to it already being busy. I'm able to fix it by simply issuing `systemctl restart home.mount` from the maintenance shell, ^d and the boot resumes normally. This is a plain Debian Jessie amd64 system, with dmcrypt and lvm2. Is this a known kernel regression that got fixed already? It's possible this is an unrelated systemd bug, but it's odd that I never saw this before this kernel. Unfortunately I've been too busy the last few weeks to spend much time on the computer in rc8+, so this is all a bit nebulous. Regards, Vito Caputo