public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Tomek Kruszona <bloodyscarion@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: xfs_repair stops on "traversing filesystem..."
Date: Fri, 10 Jul 2009 19:36:14 -0500	[thread overview]
Message-ID: <4A57DE7E.8080901@sandeen.net> (raw)
In-Reply-To: <4A57D252.4020804@gmail.com>

Tomek Kruszona wrote:

...

> I made some tests and it seems, that filesystem to finish xfs_repair
> needs to be repaired with bhash=1024... With default options it still
> hangs on "traversing filesystem..." Is it possible to change this
> behavior to normal in other way than reformat? 

It has nothing to do w/ the format, it's just internal to xfs_repair
while it's running, the way it caches blocks that it has recently used.

> Moreover I spotted some
> strange thing. 16GB of data has been moved to lost+found. I tried to

Yeah ...

> clean L+F by
> # rm -rf lost+found
> 
> but suddenly I got this:
> 
> # ls -l /mnt/storage/
> ls: cannot access /mnt/storage/lost+found: No such file or directory
> total 0
> drwxr-xr-x 4 root    root 33 Mar  4 17:21 l_mirror
> ?????????? ? ?       ?     ?            ? lost+found

huh.  let me try on the repaired metadata image...

[root@bear-05 bad-repair]# mount -o loop badfs.img mnt/
[root@bear-05 bad-repair]# du -hc mnt/lost+found/
26M	mnt/lost+found/1602304
5.0M	mnt/lost+found/2558868
18G	mnt/lost+found/
18G	total
[root@bear-05 bad-repair]# rm -rf mnt/lost+found/*
[root@bear-05 bad-repair]# ls -l mnt/
total 0
drwxr-xr-x 4 root root 33 Mar  4 10:21 ??5?t??4
drwxr-xr-x 0 root root  6 Jul 10 19:48 lost+found
drwxr-xr-x 2 1000 root  6 Jun 30 08:45 tests

Did you do something else to the fs in between?

> I had to run xfs_repair (bhash=1024) once again and then l+f disappeared...
> 
> So I started to think: does it have some influence on data that are
> stored on this filesystem? I'm afraid that files on this FS may become
> inconsistent :/

Well, I don't know what has gone wrong with your filesytem (or, with the
storage beneath it, or whatever) - but it is certainly possible that
with corrupted metadata, that there is corrupted data as well - all
depends on the root cause ...

-Eric

> Best regards,
> Tomasz Kruszona

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

      reply	other threads:[~2009-07-11  0:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-09 14:13 xfs_repair stops on "traversing filesystem..." Tomek Kruszona
2009-07-09 14:54 ` Eric Sandeen
2009-07-09 15:03   ` Tomek Kruszona
2009-07-10  5:28 ` Eric Sandeen
2009-07-10  7:27   ` Tomek Kruszona
2009-07-10 14:35     ` Eric Sandeen
2009-07-10 20:17     ` Eric Sandeen
2009-07-10 21:02       ` Tomek Kruszona
2009-07-10 21:15         ` Eric Sandeen
2009-07-10 23:44           ` Tomek Kruszona
2009-07-11  0:36             ` Eric Sandeen [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=4A57DE7E.8080901@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=bloodyscarion@gmail.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