xfs
[Top] [All Lists]

Re: 5 concurrent bonnie runs failing after first pass .

To: "Mr. James W. Laferriere" <babydr@xxxxxxxxxxxxxxxx>
Subject: Re: 5 concurrent bonnie runs failing after first pass .
From: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Thu, 21 Aug 2008 01:32:03 -0500
Cc: xfs@xxxxxxxxxxx, linux-raid maillist <linux-raid@xxxxxxxxxxxxxxx>, Dan Williams <dan.j.williams@xxxxxxxxx>
In-reply-to: <Pine.LNX.4.64.0808201853480.26204@xxxxxxxxxxxxxxxxxxxxxxxxx>
References: <Pine.LNX.4.64.0808201853480.26204@xxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: Thunderbird 2.0.0.16 (Macintosh/20080707)
Mr. James W. Laferriere wrote:
>       Hello Dave (& Dan & All) ,
>       Even with your patch to xfs (49641f1acfdfd437ed9b0a70b86bf36626c02afe) 
> Under some conditions multiple concurrent bonnie runs just halt .  No log to 
> dmesg or serial console .  But there is a message from something when bonnie 
> halts . 

that "something" == bonnie ...

>  Also note the really low I/O .
> 
> 
> --- Bad Bonnie --- (multiple concurrent processes)
> filesrv2,136G,,,14389,16,10165,13,,,64722,9,134.3,0,16,212,2,+++++,+++,206,2,226,1,+++++,+++,177,2
> semop: semop failed.
> : Resource temporarily unavailable
> 

Is it unique to xfs?

this is an error from bonnie's semop() call; it's not immediately clear
that there is a problem with xfs.  Is bonnie deadlocking?  Is xfs stuck?

echo w > /proc/sysrq-trigger to see if there are stuck processes and
where they are.

-Eric


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