Re: find a file containing a specific sector

[Alexander Viro]

On Wed, 23 Jan 2002, Chuck Campbell wrote:

> For the last 7 months, I've been getting the following error in 
> /var/log/messages every night during the cron.daily execution.  I've finally
> tracked it down to happening during my tripwire run, and I suspect
> (based on linear time into the run, and sizes of files) the problem file
> lies somwhere in /usr/lib.
> 
> The error message has been identical for months, so I assume I have a bad 
> spot that is not spreading.  I'd like to find the affected file, rename it
> and ignore the problem for a while longer.
> 
> If I know the sector and lbasector, can I determine the inode and/or
> the actual file affected?

find /usr/lib -type f|sed -e 's!.*!cat & >/dev/null || echo &!'|sh