From: Paul Slootman <paul@wurtel.net>
To: xfs@oss.sgi.com
Subject: Re: cache_purge: shake on cache 0x5880a0 left 8 nodes!?
Date: Mon, 14 Aug 2006 17:55:27 +0200 [thread overview]
Message-ID: <20060814155527.GA10314@wurtel.net> (raw)
In-Reply-To: <20060814145927.GA28940@tuatara.stupidest.org>
On Mon 14 Aug 2006, Chris Wedgwood wrote:
> On Thu, Aug 10, 2006 at 06:42:22PM +0200, Paul Slootman wrote:
>
> > 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
>
> do subsequent xfs_repair runs go silent? if not then you've probably
> hit a case where it's leaving something icky behind and you have to
> manually poke it using xfs_db (i had this myself)
No, these particular messages didn't reoccur, although I've been having
a lot of trouble with that filesystem (see my other message today).
Paul Slootman
prev parent reply other threads:[~2006-08-14 15:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-10 16:42 cache_purge: shake on cache 0x5880a0 left 8 nodes!? Paul Slootman
2006-08-11 1:30 ` 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 [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=20060814155527.GA10314@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