Messages in this thread | | | Date | Thu, 5 Jan 2012 08:44:43 -0800 | From | Tejun Heo <> | Subject | Re: Revoking filesystems [was Re: Sysfs attributes racing with unregistration] |
| |
Hello,
On Thu, Jan 05, 2012 at 08:03:16AM -0800, Eric W. Biederman wrote: > Well the choices are really: > a) On a block device hotunplug keep the device and have it simply report > everything as errors, to the filesystem. Maybe with a hint to the > filesystem that something is wrong. > b) Have a filesystem revoke method so that we don't have to keep the > unplugged block device structure around indefinitely. > > It seems clear that we are neither doing (a) or (b) which results in > periodic and spectacular failures when block devices are unplugged, > because we try and access block devices that no longer exist.
We're definitely doing a). If it's not working properly, it's a bug.
Thanks.
-- tejun
| |