store_content problems?
Matt Mankins
matt at ka-zam.com
Tue Jan 16 04:11:10 UTC 2007
Ah, found the problem. My new machines didn't have NTP running on
them, so the disks were timing/aging out.
Phew!
I started a stub here for common problems:
http://mogilefs.schtuff.com/debugging_usage_problems
Thanks for the help.
Matt
On Jan 15, 2007, at 6:09 PM, Matt Mankins wrote:
> mogstored is running as root.
>
> root 13741 0.1 0.4 12312 8556 pts/0 Sl 16:21 0:09 /
> usr/local/bin/perl -w /usr/local/bin/mogstored
>
> /var/mogdata/devN/* is owned by root as well.
>
> ls -laR /var/mogdata/dev1/0/000/
>
> /var/mogdata/dev1/0/000/:
> total 12
> drwxr-xr-x 3 root root 4096 Jan 5 11:17 .
> drwxr-xr-x 3 root root 4096 Jan 5 11:17 ..
> drwxr-xr-x 2 root root 4096 Jan 14 20:56 000
>
> /var/mogdata/dev1/0/000/000:
> total 184
> drwxr-xr-x 2 root root 4096 Jan 14 20:56 .
> drwxr-xr-x 3 root root 4096 Jan 5 11:17 ..
> -rw-r--r-- 1 root root 3 Jan 5 11:17 0000000001.fid
> -rw-r--r-- 1 root root 17 Jan 5 11:29 0000000008.fid
> -rw-r--r-- 1 root root 34651 Jan 9 13:00 0000000017.fid
> -rw-r--r-- 1 root root 61893 Jan 9 13:13 0000000018.fid
> -rw-r--r-- 1 root root 12 Jan 11 15:31 0000000023.fid
> -rw-r--r-- 1 root root 54647 Jan 12 18:29 0000000043.fid
> .
> .
> .
> Thanks for the help so far!
>
> On Jan 15, 2007, at 5:12 PM, Brad Fitzpatrick wrote:
>
>> Does the user mogstored is running as have permission to write to
>> files on
>> /var/mogdata/devN/* ? Does that user own the /var/mogdata/devN
>> directory?
>>
>>
>> On Mon, 15 Jan 2007, Matt Mankins wrote:
>>
>>> 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
>>>>>
>>>>>
>>>
>>>
More information about the mogilefs
mailing list