>>>>> "Ted" == Ted Ts'o <tytso@xxxxxxx> writes: Ted> Can we decide soon what the right thing should be? I'm about to Ted> release e2fsrogs 1.41.13, and if I should put in some sanity Ted> checking code so mke2fs does something sane when it sees a 1M Ted> physical block size, I can do that. I don't think it's entirely clear what the "right thing" would be. Let's ignore the 1MB block size for now. That's clearly a fluke and a buggy device. But there are SSDs that will advertise an 8KiB physical block size. And apparently 16KiB devices are in the pipeline. How do we want to handle these devices? Allowing blocks bigger than the page size is going to be painful. So the question is whether we can tweak the filesystem layout in a way that would alleviate the pain without having to change the filesystem block size in the traditional sense. At least we're talking about SSDs and arrays here. I assume the partial block write penalty for these devices would be smaller than it is for rotating media. -- Martin K. Petersen Oracle Linux Engineering -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
