Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263598AbUDOVHc (ORCPT ); Thu, 15 Apr 2004 17:07:32 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263685AbUDOVHc (ORCPT ); Thu, 15 Apr 2004 17:07:32 -0400 Received: from kinesis.swishmail.com ([209.10.110.86]:44554 "EHLO kinesis.swishmail.com") by vger.kernel.org with ESMTP id S263598AbUDOVH3 (ORCPT ); Thu, 15 Apr 2004 17:07:29 -0400 Message-ID: <407EF9C4.4070207@techsource.com> Date: Thu, 15 Apr 2004 17:08:20 -0400 From: Timothy Miller MIME-Version: 1.0 To: Linux Kernel Mailing List Subject: Overlay ramdisk on filesystem? Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 757 Lines: 19 I have a feeling that this may be a bit too off-topic, but I'm doing some Linux and hardware performance tests, and some of the tests will put the hardware into an unstable state which could get memory errors which could cause filesystem corruption. I would like to know how I could overlay a RAM disk over a read-only filesystem so that all new files and modified files end up in the RAM disk, but old files are read from the disk. This way, when I reboot, the disk reverts back. Suggestions? Thanks. - 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/