From mboxrd@z Thu Jan 1 00:00:00 1970 From: Martin Jambor Subject: What happens to pages that failed to be written to disk? Date: Thu, 28 Jul 2005 02:12:42 +0200 Message-ID: <8e70aacf05072717125bfc1c58@mail.gmail.com> Reply-To: Martin Jambor Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Return-path: Received: from zproxy.gmail.com ([64.233.162.200]:31597 "EHLO zproxy.gmail.com") by vger.kernel.org with ESMTP id S261199AbVG1AMp convert rfc822-to-8bit (ORCPT ); Wed, 27 Jul 2005 20:12:45 -0400 Received: by zproxy.gmail.com with SMTP id r28so185953nza for ; Wed, 27 Jul 2005 17:12:42 -0700 (PDT) To: linux-fsdevel@vger.kernel.org Content-Disposition: inline Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Hi, I have tried to find out how filesystems are supposed to handle the situation when an asynchronous writeout of a page fails and so had a look at the ext2 code. All I have found is that for example mpage_end_io_write sets the Error flag of both the page and its mapping... and that is about it. What happens to these pages later on? Does the memory manager attempt to write them again? Is the error somehow signalled to anyone? Do filesystems try to relocate the data from bad blocks of the device? TIA Martin Jambor