From mboxrd@z Thu Jan 1 00:00:00 1970 From: "H. Peter Anvin" Subject: ext3 -> crash -> fsck -> readlink -> oops Date: 16 May 2002 17:50:39 -0700 Sender: linux-fsdevel-owner@vger.kernel.org Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Return-path: Received: (from root@localhost) by neon-gw.transmeta.com (8.9.3/8.9.3) id RAA18658 for ; Thu, 16 May 2002 17:51:02 -0700 Received: from palladium.transmeta.com (palladium.transmeta.com [10.1.1.46]) by deepthought.transmeta.com (8.11.6/8.11.6) with ESMTP id g4H0oej18817 for ; Thu, 16 May 2002 17:50:40 -0700 (PDT) Received: (from mail@localhost) by palladium.transmeta.com (8.9.3/8.9.3) id RAA22788 for linux-fsdevel@vger.kernel.org; Thu, 16 May 2002 17:50:40 -0700 To: linux-fsdevel@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Hi there, We just suffered some SCSI bus problems on kernel.org that resulted in significant data loss on our mirror volume, but not enough to ditch the whole filesystem and start over (rsync --checksum is a good thing.) However, we keep getting oopses, ostensibly as the result of a garbaged symlink. This filesystem has been run through fsck -y (e2fstools 1.26). Oops details at: http://userweb.kernel.org/~hpa/oops-20020516/ The kernel running is 2.4.19-pre8. -hpa -- at work, in private! "Unix gives you enough rope to shoot yourself in the foot." http://www.zytor.com/~hpa/puzzle.txt