[Top] [All Lists]

Re: The mmap() problem is back

To: Wessel Dankers <wsl@xxxxxxxxxxxx>
Subject: Re: The mmap() problem is back
From: Timothy Ball <timball@xxxxxxx>
Date: Sat, 3 Aug 2002 13:36:20 -0400
In-reply-to: <20020803165941.GF576@xxxxxxxxxxxx>
References: <20020803132927.GA576@xxxxxxxxxxxx> <9862.1028384103@xxxxxxxxxxxxxxxxxxxxx> <20020803142405.GC576@xxxxxxxxxxxx> <1028390577.1131.4.camel@xxxxxxxxxxxxxxxxxxxxxxx> <20020803160859.GE576@xxxxxxxxxxxx> <1028391174.1131.8.camel@xxxxxxxxxxxxxxxxxxxxxxx> <20020803165941.GF576@xxxxxxxxxxxx>
Sender: owner-linux-xfs@xxxxxxxxxxx
User-agent: Mutt/1.5.1i
On Sat, Aug 03, 2002 at 06:59:41PM +0200, Wessel Dankers wrote:
> As I said in my other mail, it takes some trying to get it to produce the
> error. If I create different files with different sizes in different ways
> the problem *will* get triggered. I can reproduce it on two machines, one
> running 2.4.19-xfs (p200mmx, SCSI) and one 2.4.19-rc2-xfs (Athlon XP, IDE).

I was curious about the amount of error on my system mapcheck would find
(I just install using the xfs enabled debian netinst cd). Upgraded the
kernel immediately to: 

timball@kundera {74}$ uname -a
Linux kundera 2.4.19-rc3-xfs #3 Tue Jul 30 11:19:30 EDT 2002 i686 unknown 
unknown GNU/Linux

running mapcheck in my home directory (probably the busiest as far as
creat, unlink goes): 

timball@kundera {113}$ mapcheck 
Scanning current directory
15608 files scanned 2 files fixed 24 errors

running mapcheck from / gives: 

root@kundera {145}$ ~timball/bin/mapcheck 
Scanning current directory
228684 files scanned 5 files fixed 50 errors


        GPG key available on pgpkeys.mit.edu
pub  1024D/511FBD54 2001-07-23 Timothy Lu Hu Ball <timball@xxxxxxx>
Key fingerprint = B579 29B0 F6C8 C7AA 3840  E053 FE02 BB97 511F BD54

<Prev in Thread] Current Thread [Next in Thread>