From: Jay L. <jl...@sl...> - 2020-04-13 15:46:42
|
Hi, Just to provide a quick update. I confirmed that I have enough disk space and updated MooseFS to the latest and the problem persists. I see nothing in the kernel logs that coincides with these errors. The error always occurs at the top of the hour. (For example 10:00:00, 3:00:00, 21:00:00 or 18:00:00), and occurs at most every 3 hours but often less frequently than that. (The time between instances is inconsistent.) I am still scratching my head on this one. Any other ideas? JL On Fri, Apr 10, 2020 at 5:43 AM Agata Kruszona-Zawadzka <ch...@mo...> wrote: > W dniu 10.04.2020 o 01:11, Jay Livens pisze: > > Hi, > > > > I see this periodically in the logs and am not sure what it means. > > Everything seems to be working fine, but I wanted to confirm that this > > did not signal some other form of problem. > > > > I found the actual MFS code > > <https://github.com/moosefs/moosefs/blob/master/mfsmaster/bgsaver.c> > > generating this, but I am not familiar enough with C to understand what > > it means. > > Hi, > > This means your master encountered a write error while trying to save > data to a changelog file. This might mean any kind of error: during > open, write, fsync or close. Do you have enough space in your metadata > directory (usually "/var/lib/mfs", but check your config)? Is the hdd in > your master server working properly? Are there any generic (kernel) > errors surrounding this message in your logs? Are you using the latest > version of MooseFS? > > Agata > > -- > Agata Kruszona-Zawadzka > MooseFS Team > > > _________________________________________ > moosefs-users mailing list > moo...@li... > https://lists.sourceforge.net/lists/listinfo/moosefs-users > |