From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756887AbbFRSIN (ORCPT ); Thu, 18 Jun 2015 14:08:13 -0400 Received: from one.firstfloor.org ([193.170.194.197]:38101 "EHLO one.firstfloor.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755277AbbFRSIG (ORCPT ); Thu, 18 Jun 2015 14:08:06 -0400 Date: Thu, 18 Jun 2015 20:08:04 +0200 From: Andi Kleen To: Mike Snitzer Cc: Andi Kleen , linux-kernel@vger.kernel.org, dm-devel@redhat.com Subject: Re: WARNING: at fs/block_dev.c:5 when removing LV on removed device Message-ID: <20150618180804.GC19417@two.firstfloor.org> References: <20150618165713.GB19417@two.firstfloor.org> <20150618180408.GD2321@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150618180408.GD2321@redhat.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > Hmm, so you have a filesystem active on it too? I unmounted it before. > > > Also the VG removal did not work of course. > > Once you resolve the filesystem piece, from vgremove man page: > > "vgremove allows you to remove one or more volume groups. If one or > more physical volumes in the volume group are lost, consider vgreduce > --removemissing to make the volume group metadata consistent again." Well in any case there should not be WARN()s. -Andi -- ak@linux.intel.com -- Speaking for myself only.