All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Hendrik Hoeth <hendrik.hoeth@cern.ch>
Cc: xfs@oss.sgi.com
Subject: Re: corrupt file system -- "Structure needs cleaning"
Date: Fri, 26 Jun 2009 16:52:55 -0500	[thread overview]
Message-ID: <4A454337.6030100@sandeen.net> (raw)
In-Reply-To: <20090626212611.GI29416@mail.physik.uni-wuppertal.de>

Hendrik Hoeth wrote:
> Thus spake Eric Sandeen (sandeen@sandeen.net):
> 
>>> [14:44] root@jetway:/var/log # xfs_check /dev/mapper/hda_crypt_vg-home
>> xfs_check doesn't actually fix anything; I'd run xfs_repair.  Use -n
>> first if you want to see what it would do.
> 
> I thought that if xfs_check doesn't show any errors, the filesystem is
> fine and doesn't need an xfs_repair. Is that wrong?

Well, yes, I suppose that's true.

I almost never use xfs_check mostly because it's a memory hog, still,
and xfs_repair checks almost everything that xfs_check does (and what
isn't checked is rebuilt anyway)

> Anyway xfs_repair looks healthy to me:

good news, I guess :)

-Eric

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2009-06-26 21:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-26 19:58 corrupt file system -- "Structure needs cleaning" Hendrik Hoeth
2009-06-26 20:17 ` Eric Sandeen
2009-06-26 21:26   ` Hendrik Hoeth
2009-06-26 21:52     ` Eric Sandeen [this message]
2009-06-26 20:36 ` Felix Blyakher
2009-06-26 21:21   ` Hendrik Hoeth
2009-06-27  7:08   ` Hendrik Hoeth
2009-06-27 15:00     ` Felix Blyakher
     [not found] <378225748.635911246250987189.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
2009-06-29  4:50 ` Lachlan McIlroy

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=4A454337.6030100@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=hendrik.hoeth@cern.ch \
    --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 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.