Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752289Ab0LPMbF (ORCPT ); Thu, 16 Dec 2010 07:31:05 -0500 Received: from rcsinet10.oracle.com ([148.87.113.121]:19828 "EHLO rcsinet10.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751305Ab0LPMbC (ORCPT ); Thu, 16 Dec 2010 07:31:02 -0500 Content-Type: text/plain; charset=UTF-8 From: Chris Mason To: Dave Chinner Cc: Jon Nelson , Mike Snitzer , Matt , Milan Broz , Andi Kleen , linux-btrfs , dm-devel , Linux Kernel , htd , htejun , linux-ext4 Subject: Re: hunt for 2.6.37 dm-crypt+ext4 corruption? (was: Re: dm-crypt barrier support is effective) In-reply-to: <20101216033718.GM9925@dastard> References: <1291747731-sup-3099@think> <1291751698-sup-9297@think> <1291754340-sup-1631@think> <1291755258-sup-8760@think> <1291810586-sup-8211@think> <20101216033718.GM9925@dastard> Date: Thu, 16 Dec 2010 07:29:58 -0500 Message-Id: <1292502095-sup-3835@think> User-Agent: Sup/git Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1062 Lines: 27 Excerpts from Dave Chinner's message of 2010-12-15 22:37:18 -0500: > On Wed, Dec 08, 2010 at 07:20:24AM -0500, Chris Mason wrote: > > > > Usually the trick to reproducing filesystem corruptions is adding memory > > pressure. The corruption is probably a bad interaction between reads > > and writes, and we need to make sure the reads actually happen. > > > > http://oss.oracle.com/~mason/pin_ram.c > > > > gcc -Wall -o pin_ram pin_ram.c > > > > pin_ram -m 80%-of-your-ram-in-mb > > Implemented in xfstests about 10 years ago: > > http://git.kernel.org/?p=fs/xfs/xfstests-dev.git;a=blob;f=src/usemem.c;h=b8794a6b209cebf8dbf312a8ef131e2e54b18d29;hb=HEAD But mine can use shm! I don't remember adding it, so it must have grown there while it sat on the oracle servers. Our own special Christmas magic. -chris -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/