Re: _isofs_bmap: block >= EOF (21, 24366)
David Odin (David.Odin@bigfoot.com)
Sat, 9 Oct 1999 16:57:07 +0200
On Sat, Oct 09, 1999 at 04:33:14PM +0200, Gaddoni Marco wrote:
>
> Hello!
>
> I get a number of error of this type every time i read
> any file with my cdrom:
>
> _isofs_bmap: block >= EOF (138, 230276)
> _isofs_bmap: block >= EOF (139, 230276)
> _isofs_bmap: block >= EOF (140, 230276)
> _isofs_bmap: block >= EOF (141, 230276)
> _isofs_bmap: block >= EOF (142, 230276)
> _isofs_bmap: block >= EOF (143, 230276)
> _isofs_bmap: block >= EOF (144, 230276)
> _isofs_bmap: block >= EOF (145, 230276)
> _isofs_bmap: block >= EOF (146, 230276)
> _isofs_bmap: block >= EOF (147, 230276)
> _isofs_bmap: block >= EOF (148, 230276)
> _isofs_bmap: block >= EOF (149, 230276)
> _isofs_bmap: block >= EOF (150, 230276)
> _isofs_bmap: block >= EOF (151, 230276)
> _isofs_bmap: block >= EOF (152, 230276)
> _isofs_bmap: block >= EOF (153, 230276)
> _isofs_bmap: block >= EOF (154, 230276)
>
> I have no problem to read the file.
>
AFAIK, this message is harmless. It's due to a bug in the read ahead code,
(Davem, correct me if I'm wrong) which try to read beyond the end of a file.
This problem is general to every filesystems, but isofs is the only one I know
which complains about this.
If these messages bug you, you can comment out the printk which generate it
in linux/fs/isofs/inode.c (search for _iso_bmap).
This is not a fix, it just hide the symptoms, but as long it's the only
symptom so far, you can just hide it :)
DindinX
--
David.Odin@bigfoot.com
When you become used to never being alone, you may consider yourself
Americanized.
-
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/