* dd of=blkdev seek=123 -> EINVAL ??
@ 2001-12-17 1:00 Matti Aarnio
2001-12-17 1:29 ` Matti Aarnio
0 siblings, 1 reply; 2+ messages in thread
From: Matti Aarnio @ 2001-12-17 1:00 UTC (permalink / raw)
To: linux-kernel
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: dd of=blkdev seek=123 -> EINVAL ??
2001-12-17 1:00 dd of=blkdev seek=123 -> EINVAL ?? Matti Aarnio
@ 2001-12-17 1:29 ` Matti Aarnio
0 siblings, 0 replies; 2+ messages in thread
From: Matti Aarnio @ 2001-12-17 1:29 UTC (permalink / raw)
To: linux-kernel
On Mon, Dec 17, 2001 at 03:00:28AM +0200, Matti Aarnio wrote:
> With recent dd (4.0p) and 2.4.17rc1 an attempt to write (with DD)
> into a block-device yields EINVAL error.
With dd 4.1.3 the problem no longer exists.
That newer version does fstat() on file, and notices that
it is, indeed, a device.
End of problem.
But why I am seeing mysterious total hangs of this kernel is
another story, and probably related to memory allocation...
/Matti Aarnio
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2001-12-18 13:29 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-12-17 1:00 dd of=blkdev seek=123 -> EINVAL ?? Matti Aarnio
2001-12-17 1:29 ` Matti Aarnio
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®