public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Slootman <paul@wurtel.net>
To: xfs@oss.sgi.com
Subject: Re: cache_purge: shake on cache 0x5880a0 left 8 nodes!?
Date: Sat, 12 Aug 2006 11:14:51 +0200	[thread overview]
Message-ID: <20060812091451.GA16661@wurtel.net> (raw)
In-Reply-To: <20060811090218.GB22934@wurtel.net>

On Fri 11 Aug 2006, Paul Slootman wrote:
> 
> Unfortunately, the filesystem panicked again last night.
> This was after the double repair, and rebooting into 2.6.17.7, which
> shouldn't have the bug, right?
> I'll run another repair now :-(

And again.
Curious fact appeared: the lost+found directory from the first time
(which I had moved to lost+found.x) could not be removed "Directory not
empty". This would indicate that the CVS repair version (of 2 days ago)
does not properly build the lost+found directory.

I've now zapped that directory with xfs_db, and am running the (daily?!)
xfs_repair at this moment. As the filesystem is 1.1TB, it takes a couple
of hours :(


Paul Slootman

  reply	other threads:[~2006-08-12  9:16 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 [this message]
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=20060812091451.GA16661@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