public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Steigerwald <Martin@lichtvoll.de>
To: linux-xfs@oss.sgi.com
Subject: Re: Problem with xfs_repair
Date: Sat, 29 Jul 2006 14:57:19 +0200	[thread overview]
Message-ID: <200607291457.20760.Martin@lichtvoll.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0607281023370.30325@p34.internal.lan>

Am Freitag 28 Juli 2006 16:23 schrieb Justin Piszcz:

> > Is your knoppix boot cd 5.0.1 == 2.6.17 == bugged kernel? ;P
>
> When repairing, do not use knoppix 5.0.1 or any version that uses
> 2.6.17 either..

Hello Justin,

since xfs_repair works independently of the in-kernel XFS implementation 
it is possible to repair a directory-corruption broken XFS filesystem 
with Knoppix 5.0.1.

It did so already. I used 5.0.1 to rsync a workstation image and sure it 
had this slight corruption afterwards. Thus I xfs_repair'ed it and 
xfs_check'ed it afterwards and all was well again.

No this is not a recommendation to use Knoppix 5.0.1 to rsync an 
workstation image ;), but an xfs_repair should be possible (unless one 
hits the unfixable bug). 

Important: When XFS needs to be mounted first before repair in order to 
clean the log it might not be wise to use Knoppix 5.0.1 tough.

BTW when using Knoppix 5 or even an older version instead I recommend 
switching off the write cache to be on the safe side (hdparm -W0).

Regards,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7

      reply	other threads:[~2006-07-29 12:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-28  6:45 Problem with xfs_repair Ralf Hildebrandt
2006-07-28  7:01 ` Barry Naujok
2006-07-28  8:29   ` Ralf Hildebrandt
2006-07-28 14:35     ` Martin Steigerwald
2006-07-28 14:19 ` Justin Piszcz
2006-07-28 14:23   ` Justin Piszcz
2006-07-29 12:57     ` 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=200607291457.20760.Martin@lichtvoll.de \
    --to=martin@lichtvoll.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox