Bug#11922: closed by maximilian attems <max@stro.at> (Re: Bug#11922: I/O error on blank tapes)
On Sat, Feb 09, 2008 at 03:05:38PM +0000, Ian Jackson wrote:
> reopen 11922
> thanks
>
> Debian Bug Tracking System writes ("Bug#11922 closed by maximilian attems <max@stro.at> (Re: Bug#11922: I/O error on blank tapes)"):
> > On Tue, 05 Feb 2008, Kai Makisara wrote:
> > > This is not a bug, it is a feature. There is _nothing_ on the tape and if
> > > you try to read something, you get an error. The same thing applies to
> > > reading after the last filemark. Note that after writing a filemark at the
> > > beginning of the tape, the situation is different. Now there is a file and
> > > the normal EOF semantics apply although there still is no data.
>
> If one takes this view, then the program which is reading the tape
> should get EOF. Obviously I disagree with that view. I think it's
> appropriate for the driver to give EIO in this case but ...
>
> > > I admit that the error return could be more descriptive but the st driver
> > > tries to be compatible with other Unices.
>
> ... IMO anything that gives EIO should also generate a log message to
> say why.
>
> This bug report is not about the errno value passed to the userland
> program, but about the lack of a log message.
If you want to see that changed, please report this upstream. Otherwise
it just clutters the Debian kernel bugs, which are already too hard
to handle.
Cheers,
Moritz
Reply to: