Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757870AbYKUQ7o (ORCPT ); Fri, 21 Nov 2008 11:59:44 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755413AbYKUQ7g (ORCPT ); Fri, 21 Nov 2008 11:59:36 -0500 Received: from rn-out-0910.google.com ([64.233.170.190]:17450 "EHLO rn-out-0910.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755251AbYKUQ7f (ORCPT ); Fri, 21 Nov 2008 11:59:35 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=KydV86fI9EzpJbk6ZS/YuM/V8x+EeG4+gpPx0Fdj/XfGSSk/dPZ0T/GxoAZPZbjA2x VSxEBs6Oz5g5cSkjnzwzve55QtQJ6X3a2iUkYZm5tE3+lYKRvf9/2U0rulsFcdbRLkor PCv6VEwecKVHaf0fTY/qwGCZFT7ecuis+Osww= Message-ID: Date: Fri, 21 Nov 2008 11:59:32 -0500 From: "Andrey Vul" To: linux-kernel Subject: Bad inodes and ESTALE MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 464 Lines: 11 Why do files/directories located on unreadable inodes cause ESTALE when trying to access ( open()) or modify (unlink()) them? I know it's caused by a bad inode because fsck -f fixes all of the problems. -- Andrey Vul -- 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/