With recent dd and 2.4.17rc1 an attempt to write (with DD)
into a block-device yields EINVAL error.
Doing strace shows that it comes from ftruncate64()
on the opened device.
Should there be some other error code ? EBLKDEV ?
Or is the dd (4.0p) at fault, and it should either
not ask for the ftruncate*() at all, or ignore its error ?
/Matti Aarnio
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Dec 23 2001 - 21:00:15 EST