[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [dm-devel] Re: [RFC] device-mapper ioctl interface



On Thu, Jun 05, 2003 at 11:47:10AM -0500, Kevin Corry wrote:
> 1) Snapshots. Currently, the snapshot module, when it constructs a new table, 
> reads the header and existing exception tables from disk to determine the 
> initial state of the snapshot. With this new scheme, this setup really 
> shouldn't happen until the device is resumed (if it is done when the 
> "inactive" table is created, an existing "active" table could change the 
> on-disk information before the tables are switched). This kind of implies a 
> new entry-point into the target module will be required. 

See the suspend and resume target methods in my recent dev tree.
We'll have to delay the metadata reading for both the snapshots and
mirror to the first 'resume'.

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

I think removing a device that has deferred io against it should not
be possible, since it can only be in that state if the device is open.
We shouldn't start ripping devices out from under people.

The one place where we do want to do this is for the DM_REMOVE_ALL
ioctl cmd.  Which is really an emergency panic button.  I'll just
error any deferred io in this case.

- Joe



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]