From mboxrd@z Thu Jan 1 00:00:00 1970 From: Martin Jambor Subject: Re: What happens to pages that failed to be written to disk? Date: Sat, 30 Jul 2005 21:47:36 +0200 Message-ID: <8e70aacf050730124739a9382@mail.gmail.com> References: <8e70aacf05072717125bfc1c58@mail.gmail.com> <20050728003326.4add1a0f.akpm@osdl.org> Reply-To: Martin Jambor Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Cc: linux-fsdevel@vger.kernel.org Return-path: Received: from zproxy.gmail.com ([64.233.162.199]:17735 "EHLO zproxy.gmail.com") by vger.kernel.org with ESMTP id S263153AbVG3Trh convert rfc822-to-8bit (ORCPT ); Sat, 30 Jul 2005 15:47:37 -0400 Received: by zproxy.gmail.com with SMTP id r28so624158nza for ; Sat, 30 Jul 2005 12:47:36 -0700 (PDT) To: Andrew Morton In-Reply-To: <20050728003326.4add1a0f.akpm@osdl.org> Content-Disposition: inline Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Hi and thanks for all answers. On 7/28/05, Andrew Morton wrote: > > Is the error > > somehow signalled to anyone? > > Yes, it's propagated into the file's address_space for a later > fsync()/fdatasync()/msync() to detect. I see, so a subsequent sync, fsync or umount fail with an error even when the writing that failed was not initiated because of them? > > Do filesystems try to relocate the data > > from bad blocks of the device? > > Nope. Disks will do that internally. If a disk gets a write I/O error > it's generally dead. I am not interested in what happens in HW, I strive to write a filesystem :-) Anyway, I see that a write error probably does not happen because of bad blocks anyway but because something even worse happened and therefore there is no point in it even though our filesystem would be able to relocate stuff fairly easily. Am I right? Thanks again, Martin