On Thu, 11 Feb 1999 10:31:57 +0100 (MET), Andries.Brouwer@cwi.nl said:
> But it is an internal kernel bug. User space doesnt know about it.
> An ioctl cannot help.
> (At most it can help in avoiding the problem, just like my solution:
> `mount ... -o blocksize=1024' helps in avoiding the problem.)
> No, we do not want ioctls. The kernel must be fixed.
No. There is no way I'll support the idea of making set_blocksize
preserve data in the buffer cache. That is just brain-dead. So if
you want to go and change every filesystem in the kernel to support
non-local blocksizes, go right ahead.
The "right" fix is to make set_blocksize fail on an in-use ramdisk,
NOT to support changing the blocksize for existing buffers. Allowing
the user to set a correct blocksize via ioctl before mkfsing the
device in the first place makes a ton of sense, however.
--Stephen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/