Re: [Moosefs-users] fs_writechunk returns status 11

[Brent A N. <br...@ph...>]

By some near miraculous coincidence, my subject linked up with a thread 
from a year ago, which explained that the message is due to an attempt to 
write to a chunk that is already locked for writing by something else.

I'm guessing that Google Chrome, with its highly threaded nature, kind of 
trips over itself when it comes to the cache, sometimes generating huge 
bursts of warnings from MooseFS (it really can quickly fill /var). 
Otherwise, you'd probably run into this when running two programs that try 
to write to the same file, which should be rare and not really an issue.

It's a pity that Chrome doesn't have some file to edit so that you can set 
system-wide defaults, but the '--disk-cache-dir="/dev/null"' command-line 
option does look promising (and, as I mentioned in the Firefox thread, it 
seems to give Chrome a substantial speed boost when running on MooseFS).

On Wed, 28 Mar 2012, Steve Thompson wrote:

> On Tue, 27 Mar 2012, Brent A Nelson wrote:
>
>> Mar 23 07:02:01 somehost mfsmount[31484]: file: 4282810, index: 0 -
>> fs_writechunk returns status 11
>
> I've seen exactly one occurrence of this in the two months that I have been 
> using MooseFS (CentOS 5.7, mfs 1.6.20). We don't use Google Chrome, so it 
> wasn't that in my case. I don't know the cause.
>
> Steve
>