On Thu, Jul 23, 2015 at 03:10:43PM +1000, Dave Chinner wrote: [..] > I don't think knowing the bdev timeout is necessary because the > default is most likely to be "fail fast" in this case. i.e. no > retries, just shut down. IOWs, if we describe the configs and > actions in neutral terms, then the default configurations easy for > users to understand. i.e: > > bdev enospc XFS default > ----------- ----------- > Fail slow Fail fast > Fail fast Fail slow > Fail never Fail never, Record in log > EOPNOTSUPP Fail never > > With that in mind, I'm thinking I should drop the > "permanent/transient" error classifications, and change it "failure > behaviour" with the options "fast slow [never]" and only the slow > option has retry/timeout configuration options. I think the "never" > option still needs to "fail at unmount" config variable, but we > enable it by default rather than hanging unmount and requiring a > manual shutdown like we do now....
I am wondering instead of 4 knobs (fast,slow,never,retry-timeout) can we just do with one knob per error type and that is retry-timout. retry-timeout=0 (Fail fast) retry-timeout=X (Fail slow) retry-timeout=-1 (Never Give up). Also do we really need this timeout per error type. Also would be nice if this timeout was configurable using a mount option. Then we can just specify it during mount time and be done with it. Idea of auto tuning based on what block device is doing sounds reasonable but that should not be a requirement for this patch and can go in even later. It is one of those nice to have features. Thanks Vivek -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
