Problems latest CVS source.
Drop Box
publicdropbox at gmail.com
Tue Mar 28 18:35:37 UTC 2006
FWIW, I ran into this issue yesterday on a new installation (on a new set of
systems). The issue was that max_disk_age was being exceeded, so no devices
were being returned as valid. The monitor process, in its sql call to
update the device table, sets 'mb_asof = UNIX_TIMESTAMP()', which means the
db server sets the time for that field. It turned out that the db server
hadn't been configured to use ntp and was about eight minutes behind. The
default max_disk_age is five minutes, hence the no_devices error. Not sure
if you were running into the same thing, but it's something to keep in mind.
HTH.
On 3/8/06, Arnoud Vermeer <a.vermeer at freshway.biz> wrote:
>
> Dear readers,
>
> I've upgraded my mogileFS installation to the latest CVS sources, but
> now I am encountering a problem. I get the following error when trying
> to create a file:
>
> CREATE_OPEN domain=snuffelsnel&key=1471254036.jpg&class=fotos
> ERR no_devices
>
> But I've got enough free space / devices as I can demonstrate:
>
> mfs1:/home/funzoneq# mogadm -c /etc/mogilefs/mogadm.conf check
> Checking trackers...
> 81.171.x.x:7001 ... OK
> 81.171.x.x:7001 ... OK
>
> Checking hosts...
> [ 2] mfs3.example.org ... OK
> [ 3] mfs4.example.org ... OK
> [ 4] mfs1.example.org ... OK
>
> Checking devices...
> host device size(G) used(G) free(G) use%
> ---- --------------- ---------- ---------- ---------- ------
> [ 2] dev3 229.230 0.031 229.199 0.01%
> [ 2] dev4 35.996 0.493 35.503 1.37%
> [ 3] dev5 35.288 0.428 34.859 1.21%
> [ 3] dev6 35.288 0.428 34.859 1.21%
> [ 4] dev1 229.230 0.031 229.199 0.01%
> [ 4] dev2 36.027 0.594 35.433 1.65%
> ---- --------------- ---------- ---------- ---------- ------
> total: 601.058 2.006 599.053 0.33%
>
> So I went searching through the source of mogilefsd and found that
> there were some changes in
> http://cvs.danga.com/browse.cgi/wcmtools/mogilefs/server/mogilefsd
> revision 1.109 that where untested and needed feedback.
>
> Well here it is: It isn't working, and I've got no clue why not.
>
> I've completely cleaned out my entire mogileFS cluster and reinstalled
> it. This didn't fix the problem (exact same problem), so I guess it
> are the changes from revision 1.109.
>
> Could someone help me out?
>
> Thanks,
>
> Arnoud Vermeer
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.danga.com/pipermail/mogilefs/attachments/20060328/14e39381/attachment.html
More information about the mogilefs
mailing list