public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Marco Berizzi <pupilla@hotmail.com>
Cc: David Chinner <dgc@sgi.com>,
	linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: XFS shutdown in xfs_iunlink_remove() (was Re: 2.6.25: swapper: page allocation failure. order:3, mode:0x4020)
Date: Tue, 06 May 2008 08:53:57 -0500	[thread overview]
Message-ID: <482062F5.9010402@sandeen.net> (raw)
In-Reply-To: <BAY103-DAV78BE1E59193F0C8852503B2D60@phx.gbl>

Marco Berizzi wrote:
> David Chinner wrote:
> 
>> Hmmmmm - interesting. Both the reports of this problem are from
>> machines running as squid proxies. Are you using AUFS for the cache?
> 
> no, I'm using cache_dir ufs with cache_replacement_policy heap LFUDA
> 
>> You've run repair, there's not much I can look at now.
>>
>> As a suggestion, when the cache gets close to full next time, can
>> you take a metadump of the filesystem (obfuscates names and contains
>> no data) and then trigger the cache cleanup function? If the
>> filesystem falls over, I'd be very interested in getting a copy of
>> hte metadump image and trying to reproduce the problem locally.
>> (BTW, you'll need a newer xfsprogs to get xfs_metadump).
> 
> could you please tell me the exact command to run
> when this happen again?

xfs_metadump /dev/hda8 /path/to/the/image/you/are/creating

will make a metadata image of the on device hda8 and store it in the
filename given on the 2nd argument.

The idea is to catch the metadata state shortly before the cache cleanup
triggers; this might lead to a reproducible testcase (sgi guys could
then restore the metadata image, simulate the cache cleanup, see what
happens).

Thanks,
-Eric

>> Still, thank you for the information
> 
> no problem: 2.6.25 is a bit unlucky for me :-((
> 
> 
> 
> 


  reply	other threads:[~2008-05-06 13:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-05 13:41 2.6.25: swapper: page allocation failure. order:3, mode:0x4020 Marco Berizzi
2008-05-05 23:17 ` XFS shutdown in xfs_iunlink_remove() (was Re: 2.6.25: swapper: page allocation failure. order:3, mode:0x4020) David Chinner
2008-05-06  7:03   ` Marco Berizzi
2008-05-06  8:56     ` David Chinner
2008-05-06  9:25       ` Marco Berizzi
2008-05-06 13:53         ` Eric Sandeen [this message]
2008-05-15 21:41           ` Eric Sandeen
2008-05-16  7:43             ` Marco Berizzi
2008-05-07  8:45       ` Marco Berizzi

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=482062F5.9010402@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=dgc@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pupilla@hotmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox