All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Steigerwald <ms@teamix.de>
To: linux-xfs@oss.sgi.com
Subject: Re: Unfixable XFS defect - fatal error -- can't read block 16777216
Date: Mon, 17 Jul 2006 15:20:24 +0200	[thread overview]
Message-ID: <200607171520.25067.ms@teamix.de> (raw)
In-Reply-To: <200607171105.46445.ms@teamix.de>

Am Montag, 17. Juli 2006 11:05 schrieben Sie:

> I darkly recall having read about this problem here before, but I do not
> find the relevant mail anymore. Can anyone give me a pointer on where to
> look?

Hello,

I found it:
http://oss.sgi.com/bugzilla/show_bug.cgi?id=631

Mailing list thread:
XFS crashed twice, once in 2.6.16.20, next in 2.6.17, reproducable

I read that using xfs_repair 2.7.18  might help. I didnt found this in the ftp 
area thus I compiled xfsprogs 2.8.4 under Knoppix 5 and tried with that. 
Unfortunately it isn't able to fix the defect. It shows the same error 
message as the older xfs_repair in Knoppix 5.

The partition in question is 20 gigs. I can create a backup of it, but only 
with partimage which can compress, as I have no 20gig in one place free on 
that harddisk. Tell me when you are interested.

I like to know how I can fix this in place however - the manual way of fixing 
it which is described in the mailing list thread I mentioned above did not 
work according to what I read there.

If nothing else helps I will replay a backup.

Regards,
-- 
Martin Steigerwald - team(ix) GmbH - http://www.teamix.de
gpg: 19E3 8D42 896F D004 08AC A0CA 1E10 C593 0399 AE90

      reply	other threads:[~2006-07-17 13:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-17  9:05 Unfixable XFS defect - fatal error -- can't read block 16777216 Martin Steigerwald
2006-07-17 13:20 ` Martin Steigerwald [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=200607171520.25067.ms@teamix.de \
    --to=ms@teamix.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.