store_content problems?

[Matt Mankins]

RESPONSE: ERR no_devices No+devices+found+to+store+file

If I telnet in to port 6001 and try to do it manually it does the  
same thing.  Hmm.

Checking devices...
         host device            size(G)    used(G)    free(G)   use%
         ---- --------------- ---------- ---------- ---------- ------
         [ 1] dev1               65.687      5.511     60.176   8.39%
         [ 2] dev2              229.228     21.048    208.180   9.18%
         [ 3] dev3              106.282      7.073     99.209   6.65%
         [ 4] dev4              142.334      9.317    133.017   6.55%
         [ 5] dev5               70.077      2.543     67.534   3.63%
         ---- --------------- ---------- ---------- ---------- ------
                       total:   613.608     45.492    568.116   7.41%

I can see some files in the device path...

How do you check for "writability"?  It seems that the device has to  
be on a host that is reachable and has passed a test,  
Observed_writable?  Mogstore does this, right?



On Jan 15, 2007, at 3:46 PM, Brad Fitzpatrick wrote:

> What does $mogclient->errstr say after you get undef on store_content?
>
> It should say exactly that the error was.
>
>
> On Mon, 15 Jan 2007, Matt Mankins wrote:
>
>> Hi.
>>
>> We've got 2 trackers, 5 storage hosts, and 1 problem storing files:
>>
>>   my $bytes_stored = $self->{'mogile'}->store_content($mogile_key,
>> $mogile_class, $data_ref);
>>
>> bytes_stored is undef.
>>
>> I'm wondering what to look at to see where the problem is.
>>
>> When I try using new_file/doing it manually, the file handle comes up
>> as undef on the new_file method.
>>
>> read_only = 0.
>>
>> mogadm check shows everything up and running.
>>
>> I just upgraded everything to mogilefs 1.04, but the problem remains.
>>
>> Some files get stored just fine, and if we try long enough, every
>> file seems to be able to be stored.
>>
>> Sound familiar?
>>
>> Thanks.
>>
>> Matt
>>
>>