From mboxrd@z Thu Jan 1 00:00:00 1970 From: Evgeniy Polyakov Subject: Re: [PATCH 7/8] exofs: Documentation Date: Sat, 21 Mar 2009 16:26:01 +0300 Message-ID: <20090321132601.GA10099@ioremap.net> References: <49C1331D.1080805@panasas.com> <1237399858-29537-1-git-send-email-bharrosh@panasas.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Avishay Traeger , Jeff Garzik , Andrew Morton , linux-fsdevel , open-osd , linux-kernel , James Bottomley , FUJITA Tomonori To: Boaz Harrosh Return-path: Received: from cet.com.ru ([195.178.208.66]:45210 "EHLO tservice.net.ru" rhost-flags-OK-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1752914AbZCUN0G (ORCPT ); Sat, 21 Mar 2009 09:26:06 -0400 Content-Disposition: inline In-Reply-To: <1237399858-29537-1-git-send-email-bharrosh@panasas.com> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Hi. On Wed, Mar 18, 2009 at 08:10:58PM +0200, Boaz Harrosh (bharrosh@panasas.com) wrote: > +++ b/fs/exofs/BUGS > @@ -0,0 +1,3 @@ > +- Out-of-space may cause a severe problem if the object (and directory entry) > + were written, but the inode attributes failed. Then if the filesystem was > + unmounted and mounted the kernel can get into an endless loop doing a readdir. Does it also mean that damaged media may end up freezing the machine during the mount? -- Evgeniy Polyakov