From: Paul Slootman <paul@wurtel.net>
To: xfs@oss.sgi.com
Subject: cache_purge: shake on cache 0x5880a0 left 8 nodes!?
Date: Thu, 10 Aug 2006 18:42:22 +0200 [thread overview]
Message-ID: <20060810164222.GA16332@wurtel.net> (raw)
Hi,
I had problems due to the well-known endian bug.
I first ran xfs_repair on it from the standard Debian package,
version 2.6.20. That gave a lot of output (which can be found at
http://www.xs4all.nl/~wurtel2/xfs_repair.out.4 ).
While that was running, I got today's CVS version and built that
(it reports version 2.8.11). I ran that version against the
just-repaired filesystem, and got a number of additional errors,
notably:
empty data block 10 in directory inode 1343747104: junking block
empty data block 11 in directory inode 1343747104: junking block
empty data block 12 in directory inode 1343747104: junking block
free block 16777216 entry 10 for directory ino 1343747104 bad
rebuilding directory inode 1343747104
This 7 times; additionally, this was mentioned a couple of times:
cache_purge: shake on cache 0x5880a0 left 8 nodes!?
In fact, twice before the final "done.".
The second repair output can be found at
http://www.xs4all.nl/~wurtel2/xfs_repair.out.4b .
Should I be worried about that? I tried a search for "shake on cache"
and found zero hits...
Additionally, the hash hit rates seem pretty bad. Anything to be
worried about, and could anything be done about it?
thanks,
Paul Slootman (please CC me on responses)
next reply other threads:[~2006-08-10 18:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-10 16:42 Paul Slootman [this message]
2006-08-11 1:30 ` cache_purge: shake on cache 0x5880a0 left 8 nodes!? Barry Naujok
2006-08-11 9:02 ` Paul Slootman
2006-08-12 9:14 ` Paul Slootman
2006-08-14 14:17 ` XFS internal error XFS_WANT_CORRUPTED_GOTO Paul Slootman
2006-08-15 11:54 ` Paul Slootman
2006-08-15 1:49 ` cache_purge: shake on cache 0x5880a0 left 8 nodes!? Barry Naujok
2006-08-15 11:55 ` Paul Slootman
2006-08-14 14:59 ` Chris Wedgwood
2006-08-14 15:55 ` Paul Slootman
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=20060810164222.GA16332@wurtel.net \
--to=paul@wurtel.net \
--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