xfs
[Top] [All Lists]

Re: 2.6.16-rc6: known regressions (v2)

To: Claudio Martins <ctpm@xxxxxxxxxx>
Subject: Re: 2.6.16-rc6: known regressions (v2)
From: Nathan Scott <nathans@xxxxxxx>
Date: Mon, 20 Mar 2006 09:49:12 +1100
Cc: linux-xfs@xxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx
In-reply-to: <200603182057.10171.ctpm@xxxxxxxxxx>; from ctpm@xxxxxxxxxx on Sat, Mar 18, 2006 at 08:57:09PM +0000
References: <Pine.LNX.4.64.0603111551330.18022@xxxxxxxxxxx> <20060317143642.GJ3914@xxxxxxxxx> <200603182057.10171.ctpm@xxxxxxxxxx>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.2.5i
On Sat, Mar 18, 2006 at 08:57:09PM +0000, Claudio Martins wrote:
>   Hi Adrian, Nathan and all,
> 
>  If think I might have hit this one! 

OK - any hints that might lead us toward a test case?

> I managed to get an oops which showed xfs related functions on the backtrace. 
> The process involved was "rm" and the specific stress test was some 32 
> paralell kernel builds (each one with "make -j8") on a quad Opteron box with 
> a 1 TB xfs filesystem. Preemption was disabled.

>  After that the machine was still alive, but an fsck.xfs after a reboot 
> showed 
> corruption that I was able to repair with xfs_repair. This was also with an 

Hmm, fsck.xfs wont report corruption - did you mean xfs_check?

> almost empty filesystem, hence the similarity with the above bug report.

Well, not sure its the same yet - what was your stack trace & did
repair report inodes with nlink==0?

> I didn't record the oops and output from xfs_repair. I'll update my git tree 

Ah, doh.

> tonight, rebuild and retest in hopes to find that oops again.

Great, thanks!

cheers.

-- 
Nathan


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