From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Mike Snitzer" Subject: forced umount? Date: Fri, 16 Mar 2007 23:06:52 -0500 Message-ID: <170fa0d20703162106v47dc13e1u1ae5381576f372ed@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org Return-path: Received: from wr-out-0506.google.com ([64.233.184.226]:11435 "EHLO wr-out-0506.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753722AbXCQEGy (ORCPT ); Sat, 17 Mar 2007 00:06:54 -0400 Received: by wr-out-0506.google.com with SMTP id 41so758361wry for ; Fri, 16 Mar 2007 21:06:53 -0700 (PDT) Content-Disposition: inline Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org I'm interested in understanding the state of Linux with regard to _really_ forcing a filesystem to unmount. There is a (stale) project at OSDL that has various implementations: http://developer.osdl.org/dev/fumount/ Its fairly clear that these efforts (e.g. badfs patches) haven't been given serious consideration for upstream inclusion. Do others see value in the ability to _reliably_ force a umount by having Linux discard all IOs, open files, dirty inode buffers, etc of a "bad" blockdevice? The goal is to not impact the availability or integrity of Linux while doing so. Is this forced umount work even considered worthwhile by the greater Linux community? Is anyone actively working on this? Mike