From: "Håkan Lindqvist" <lindqvist@netstar.se>
To: xfs@oss.sgi.com
Subject: xfs_repair said "cache_purge: shake on cache 0x80f5288 left 1 inodes!?"
Date: Thu, 28 Sep 2006 17:49:25 +0200 [thread overview]
Message-ID: <1159458565.28220.12.camel@lasse> (raw)
[-- Attachment #1: Type: text/plain, Size: 692 bytes --]
Hi!
When I ran xfs_repair (2.8.11) to fix a filesystem that had been bitten
by the Linux 2.6.17.<7 bug the following happened:
All seemed to go well, xfs_repair found the problematic directory inode
and rebuilded it.
At the end (right before printing "done"), it did however say
"cache_purge: shake on cache 0x80f5288 left 1 inodes!?" thrice.
The filesystem appears to be fine so far (and the directory that
previously caused the filesystem to shut down is ok again), but that
error/warning message sounded a little scary.
Is this problem harmless or should I be worried?
Regards,
Håkan Lindqvist
(Please CC me on any replies as I'm not subscribed to the list.)
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3165 bytes --]
next reply other threads:[~2006-09-28 17:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-28 15:49 Håkan Lindqvist [this message]
2006-09-29 0:54 ` xfs_repair said "cache_purge: shake on cache 0x80f5288 left 1inodes!?" Barry Naujok
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=1159458565.28220.12.camel@lasse \
--to=lindqvist@netstar.se \
--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