| To: | "David Chinner" <dgc@xxxxxxx> |
|---|---|
| Subject: | Re: XFS shutdown in xfs_iunlink_remove() (was Re: 2.6.25: swapper: page allocation failure. order:3, mode:0x4020) |
| From: | "Marco Berizzi" <pupilla@xxxxxxxxxxx> |
| Date: | Tue, 6 May 2008 11:25:21 +0200 |
| Cc: | "David Chinner" <dgc@xxxxxxx>, <linux-kernel@xxxxxxxxxxxxxxx>, <xfs@xxxxxxxxxxx> |
| References: | <BAY103-DAV7CF38DF784B82EC3F2CFAB2D70@phx.gbl> <20080505231754.GL155679365@sgi.com> <BAY103-DAV584F4B005A4F9B7B5E19CB2D60@phx.gbl> <20080506085632.GT155679365@sgi.com> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
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? > Still, thank you for the information no problem: 2.6.25 is a bit unlucky for me :-(( |
| Previous by Date: | Re: XFS shutdown in xfs_iunlink_remove() (was Re: 2.6.25: swapper: page allocation failure. order:3, mode:0x4020), David Chinner |
|---|---|
| Next by Date: | Re: [PATCH] fix dir2 shortform structures on ARM old ABI, Eric Sandeen |
| Previous by Thread: | Re: XFS shutdown in xfs_iunlink_remove() (was Re: 2.6.25: swapper: page allocation failure. order:3, mode:0x4020), David Chinner |
| Next by Thread: | Re: XFS shutdown in xfs_iunlink_remove() (was Re: 2.6.25: swapper: page allocation failure. order:3, mode:0x4020), Eric Sandeen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |