Who is root@baroque.co.uk ?

Meir Dukhan (meir@bis.co.il)
Wed, 08 May 1996 11:06:46 +0200

This is a multi-part message in MIME format.

Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


I receive many messages twice, one from their original sender and one
from root@baroque.co.uk.

The problem seem to be present only on linux-kernel and/or linux-scsi.

Is it a bug or something else %-)


Content-Type: message/rfc822
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Received: from nic.funet.fi (nic.funet.fi []) by quasi.bis.co.il (8.7.3/8.7.3) with ESMTP id LAA27821 for <meir@bis.co.il>; Wed, 8 May 1996 11:32:07 +0200 (IST)
Received: from vger.rutgers.edu ([]) by nic.funet.fi with ESMTP id <570-31937>; Wed, 8 May 1996 11:20:45 +0300
Received: by vger.rutgers.edu id <109102-12788>; Wed, 8 May 1996 04:16:30 -0500
Date: Sat, 4 May 1996 19:19:26 +0300 (EET DST)
Illegal-Object: Syntax error in From: address found on vger.rutgers.edu:
From: Linus Torvalds <torvalds@cs.helsinki.fi@baroque.co.uk>
^-illegal end of route address, illegal special character in phrase
X-UIDL: 831548050.000
From: <root@baroque.co.uk>
To: Michael Alan Dorman <mdorman@lot49.med.miami.edu>
Cc: linux-kernel@vger.rutgers.edu, linux-scsi@vger.rutgers.edu
Subject: Re: ext2 problems on fast-wide SCSI-2
In-Reply-To: <m0uFMVX-00027mC@lot49.med.miami.edu>
Message-Id: <Pine.LNX.3.91.960504191427.2161B-100000@linux.cs.Helsinki.FI>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Illegal-Object: Syntax error in Sender: address found on vger.rutgers.edu:
Sender: owner-linux-scsi@vger.rutgers.edu@baroque.co.uk
^-illegal special character in phrase
Sender: owner-linux-scsi@vger.rutgers.edu
Precedence: bulk
X-Mozilla-Status: 0011

On Fri, 3 May 1996, Michael Alan Dorman wrote:
> May 3 10:29:06 vineland kernel: free_one_pmd: bad directory entry
> 00400000
> sometimes in clusters of as many as 14 (though the directory entry
> number varies, it's always 00200000, 00400000 or 00800000).

This looks like a traditional one-bit memory error - either in cache or
in main memory. It should probably be all zero's (meaning "no page
directory" which is pretty normal ), but it has gotten corrupted, so..

> The message that I saw that got me to write this email (reformatted):
> EXT2-fs error (device 08:01): ext2_find_entry: bad entry in directory
> #101620: inode out of bounds - offset=12 inode=4194306, rec_len=12,
> name_len=2

The inode number is 4194306 = 0x00400002. Again, it looks like it should
probably be just a plain "2" which is the normal ext2 root inode number,
but something corrupted it and set one bit in the number (note how it's
the same 00400000 bit again..)