From: Daniel Phillips <dphillips@sistina.com>
Reply-To: dphillips@sistina.com
Organization: Sistina
To: dm-devel@sistina.com, Kevin Corry <kevcorry@us.ibm.com>,
       Linux Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [dm-devel] Re: [RFC] device-mapper ioctl interface
Date: Thu, 5 Jun 2003 19:00:37 +0200
User-Agent: KMail/1.5.2
References: <20030605093943.GD434@fib011235813.fsnet.co.uk> <200306051147.10775.kevcorry@us.ibm.com>
In-Reply-To: <200306051147.10775.kevcorry@us.ibm.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200306051900.37276.dphillips@sistina.com>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 815
Lines: 20

On Thursday 05 June 2003 18:47, Kevin Corry wrote:
> 2) Removing suspended devices. The current code (2.5.70) does not allow a
> suspended device to be removed/unlinked from the ioctl interface, since
> removing it would leave you with no way to resume it (and hence flush any
> pending I/Os). Alasdair mentioned a couple of new ideas. One would be to
> reload the device with an error-map and force it to resume, thus erroring
> any pending I/Os and allowing the device to be removed. This seems a bit
> heavy-handed.

Which is the heavy-handed part?

Regards,

Daniel

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/