On Fri, 11 Jun 1999, Maurice Hendrix wrote:
> There's a bug in the pcmcia package. I'm still figuring out what is
> happening. At some point an "Oops" appears. Now I have two questions.
>
> 1. To whom or where do I report the Oops (pcmcia related)?
Have a read of /usr/src/linux/Documentation/oops-tracing.txt
>
> 2. As a spin-off of this problem; when I reboot fsck notices a empty
inode
> or a missing inode. Something like that. I didn't write down the
message.
> Anyway, fsck says it deletes inode 4859 or something and then says
everyting
> is okay. I believe fsck, because I *think* I know what has happened.
> To verify this I need a way to find out where this inode 4859 was or
is. As
> long as I don't create any files, recreating the Oops will make fsck
delete
> this non-existent inode in the 48xx range.
> Is there a simple way to find out what file is tied to what inode?
(there's
> a man-page I'm overlooking?) I can then look at the inode of the
suspected
> file/mountpoint, recreate the Oops and see if fsck is deleting the
inode I'm
> suspecting. I think this could help in making a clearer bug-report.
>
Man debugfs. The key piece of this is near the end: SPECIFYING FILES.
Lawson
>< Microsoft free environment
This mail client runs on Wine. Your mileage may vary.
> Kernel 2.2.9, PCMCIA 3.0.9 (I think).
> --
> Maurice Hendrix
>
> snailmail: Fuji Photo Film BV Standard disclaimers apply
> Dept. P1LPI
> attn. M. Hendrix
> PO Box 90156
> 5000 LJ Tilburg
> phone: +31 13-579 1370 or fax: +31 13-579 1385
>
> - Still 19 months to go until the next millenium...
>
___________________________________________________________________
Get the Internet just the way you want it.
Free software, free e-mail, and free Internet access for a month!
Try Juno Web: http://dl.www.juno.com/dynoget/tagj.
