Here's an idea. What if we set a timer when send the first probing discard, and if it takes too long, we print an error message and then try to recover. More generally, if we can't trust a device's advertised discard parameters, maybe it makes sense to create a userspace program that benchmarks the device to determine various critical flash parameters, including "does discard really work?" "Is it hopelessly slow"', and "what is the erase block size"? This program can then send the appropriate parameters to a filesystem's mkfs program. - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
