On Mon, Nov 10, 2008 at 08:23:17PM -0500, Black_David@xxxxxxx wrote: > Dave, > > > Treating it as a reliable command (i.e. it succeeds or returns > > an error) means that we can implement filesystems that can do > > unmapping in such a way that when the array reports that it is out > > of space we *know* that there is no free space that can be unmapped. > > i.e. no need for a "defrag" tool. > > What if the filesystem block size and the array thin provisioning > chunk size don't match? It's still "defrag" time ... No, it's "fix the array implementation" time ;) It seems the point that we've made that the higher layers can be exact and robust is being ignored because it means work to make the arrays exact and robust. Following that, if the array is not robust (i.e. doesn't execute unmap commands exactly as specified), then as a filesystem developer I want to know that this occurred so that appropriate warnings can be issued to inform the admin of what they need to do when the array runs out of space.... Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
