public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Nathan Scott <nathans@sgi.com>
To: Rishi Malik <rishi.malik@adic.com>
Cc: xfs@oss.sgi.com
Subject: Re: Where are superblocks stored?
Date: Tue, 1 Aug 2006 08:27:47 +1000	[thread overview]
Message-ID: <20060801082747.B2286470@wobbly.melbourne.sgi.com> (raw)
In-Reply-To: <51A9A4FCBC06324F8BFE956A551B58E0056A4CA3@mail01dn.adic.com>; from rishi.malik@adic.com on Mon, Jul 31, 2006 at 09:23:27AM -0600

On Mon, Jul 31, 2006 at 09:23:27AM -0600, Rishi Malik wrote:
> Hi All,
> 
> I'm investigating some compact flash failures we've had. We run XFS on
> the CF. I've been getting a lot of I/O errors around logical block
> 543080. These are 512MB compact flash cards, and I think that block puts
> it at about halfway through the CF. I know the I/O errors indicate an

That would be the journal.

> error at a lower level then XFS. What I'm wondering, is if there's a
> superblock stored there? Maybe we're hammering that area a lot, and
> because of other problems with the card, we're getting these errors. 
> 
> I know that XFS stores its primary superblock at 0, but I haven't found
> out where the secondary superblocks are stored. Any help is appreciated.

The secondary superblocks are very rarely touched (repair, and
growfs only IIRC), they will be unrelated to your problem here.

cheers.

-- 
Nathan

  parent reply	other threads:[~2006-07-31 22:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-31 15:23 Where are superblocks stored? Rishi Malik
2006-07-31 19:43 ` Chris Wedgwood
2006-07-31 22:16 ` KELEMEN Peter
2006-07-31 22:27 ` Nathan Scott [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-07-31 20:17 Rishi Malik

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=20060801082747.B2286470@wobbly.melbourne.sgi.com \
    --to=nathans@sgi.com \
    --cc=rishi.malik@adic.com \
    --cc=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