mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chuck Campbell <campbell@neosoft.com>
To: linux-kernel@vger.kernel.org
Cc: campbell@neosoft.com
Subject: find a file containing a specific sector
Date: Wed, 23 Jan 2002 12:00:55 -0600	[thread overview]
Message-ID: <20020123120055.A14311@helium.inexs.com> (raw)

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?

The error message is:

Jan 23 04:24:34 helium kernel: hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } 
Jan 23 04:24:34 helium kernel: hdc: dma_intr: error=0x40 { UncorrectableError }, LBAsect=4200315, sector=4200248 
Jan 23 04:24:34 helium kernel: end_request: I/O error, dev 16:01 (hdc), sector 4200248 

as I said before, the sector number has never changed in months.


thanks,
-chuck



-- 
ACCEL Services, Inc.| Specialists in Gravity, Magnetics |  1(713)993-0671 ph.
1980 Post Oak Blvd. |   and Integrated Interpretation   |  1(713)960-1157 fax
    Suite 2050      |                                   |
 Houston, TX, 77056 |          Chuck Campbell           | campbell@neosoft.com
                    |  President & Senior Geoscientist  |

     "Integration means more than having all the maps at the same scale!"

             reply	other threads:[~2002-01-23 18:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-23 18:00 Chuck Campbell [this message]
2002-01-23 18:08 ` Mark Hahn
2002-01-23 18:29 ` Alexander Viro
2002-01-23 18:36 ` Andreas Dilger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020123120055.A14311@helium.inexs.com \
    --to=campbell@neosoft.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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®