From: Tomek Kruszona <bloodyscarion@gmail.com>
To: xfs@oss.sgi.com
Subject: Re: xfs_repair stops on "traversing filesystem..."
Date: Fri, 10 Jul 2009 09:27:27 +0200 [thread overview]
Message-ID: <4A56ED5F.10400@gmail.com> (raw)
In-Reply-To: <4A56D176.9010702@sandeen.net>
Eric Sandeen wrote:
> No fix for you yet, but it's in cache_node_get(), in the for(;;) loop,
> and it looks like cache_node_allocate() fails to get a new node and we
> keep spinning. I need to look some more at what's going on....
Hello!
Is this specific behavior for this particular broken filesystem or is it
a bug in functions you mentioned? I'm just curious :)
Best regards,
Tomasz Kruszona
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-07-10 7:27 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 [this message]
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
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=4A56ED5F.10400@gmail.com \
--to=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 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.