From: Nathan Scott <nathans@sgi.com>
To: Daniel Brahneborg <daniel.brahneborg@infoflexconnect.se>
Cc: linux-kernel@vger.kernel.org, linux-xfs@oss.sgi.com
Subject: Re: block -> name ?
Date: Tue, 13 Apr 2004 10:41:10 +1000 [thread overview]
Message-ID: <20040413104110.A176038@wobbly.melbourne.sgi.com> (raw)
In-Reply-To: <20040412084148.A11645@infoflexconnect.se>; from daniel.brahneborg@infoflexconnect.se on Mon, Apr 12, 2004 at 08:41:48AM +0200
On Mon, Apr 12, 2004 at 08:41:48AM +0200, Daniel Brahneborg wrote:
> Hi,
>
> Recently my computer running Linux kernel 2.4.25 started
> halting all of a sudden, and running badblocks a couple
> of times showed that it was caused by reading around block
> 20.200.000 on one of the SATA disks. I'll replace the
> drive eventually, but is there a way of finding out what
> file is currently residing in a specific block? I'd prefer
> something a bit more efficient than doing a 'wc' on 300GB
> of data (which also would miss all the directories). To
> make things more interesting, the disk is 1 of 4 in a RAID5
> array, and is formatted with XFS.
>
> Best regards,
See xfs_db(8) and its blockget/blockuse commands.
cheers.
--
Nathan
prev parent reply other threads:[~2004-04-13 0:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-12 6:41 Daniel Brahneborg
2004-04-13 0:41 ` Nathan Scott [this message]
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=20040413104110.A176038@wobbly.melbourne.sgi.com \
--to=nathans@sgi.com \
--cc=daniel.brahneborg@infoflexconnect.se \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
/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®