Re: [Moosefs-users] fs_writechunk returns status 11

[Michał B. <mic...@co...>]

Hi!

Error 11 means "chunk locked". It appears when several processes at
different computers try to write to the same file in parallel. You should
not be bothered by this message but it's wise to minimize occurrences of
this situation.


Kind regards
Michał Borychowski 
MooseFS Support Manager


-----Original Message-----
From: Brent A Nelson [mailto:br...@ph...] 
Sent: Tuesday, March 27, 2012 7:54 PM
To: moo...@li...
Subject: [Moosefs-users] fs_writechunk returns status 11

I've been using MooseFS 1.6.20 on 64-bit Ubuntu 10.04 for a year or so, and
it's been working rather well.  However, I get a certain type of error that
will fill my logging space from time-to-time:

Mar 23 07:02:01 somehost mfsmount[31484]: file: 4282810, index: 0 -
fs_writechunk returns status 11 Mar 23 07:02:01 somehost mfsmount[31484]:
file: 7214721, index: 0 - fs_writechunk returns status 11 Mar 23 07:02:01
somehost mfsmount[31484]: file: 7214723, index: 0 - fs_writechunk returns
status 11 Mar 23 07:02:01 somehost mfsmount[31484]: file: 7214717, index: 0
- fs_writechunk returns status 11 Mar 23 07:02:01 somehost mfsmount[31484]:
file: 7214722, index: 0 - fs_writechunk returns status 11

This will repeat in long bursts, and then be quiet for awhile (hours or
days).  The machine on which this occurs is one where MooseFS is mounted for
my home directory (Linux/Gnome environment).  I have not noticed any
corresponding errors in the server logs.  The files referenced above are all
Google Chrome cache-related.  Perhaps all such errors have been from Google
Chrome files; most or all that I've looked at previously have been.

I'd like to move other users' home directories to MooseFS.  It's been doing
fine for non-home directories, but this error filling the logs (but not
having any other obvious impact) looks to be a small obstacle for home
directories.  There is also the Openoffice bug which cause it to break with
MooseFS, but I can get all the rest of my machines over to LibreOffice
without much trouble. We want to be on LibreOffice, anyway.

Does anyone know what causes the "fs_writechunk returns status 11" 
complaints? Is it already fixed in the new release? Is it specific to Google
Chrome (and perhaps its fault), or is it just that Google Chrome is active
more than anything else, at all times, and is therefore more prone to
glitches?

Thanks,

Brent Nelson
Director of Computing
Dept. of Physics
University of Florida

----------------------------------------------------------------------------
--
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
moosefs-users mailing list
moo...@li...
https://lists.sourceforge.net/lists/listinfo/moosefs-users