[Ocfs2-users] OCFS2 and Apache Problem

Michael Moody michael at gsc.cc
Tue Nov 13 18:18:25 PST 2007


It's a fairly sizable filesystem, with 10's of thousands of little 
files, and thousands of directories.

Also, given as it's an apache server node, the ls -l test would likely 
be inconclusive.

However, I forgot to mention it, my stupid mistake, I had this happen in 
some of my directories:

pba1 profilepic # ls -l 6*
ls: cannot access 67705.jpg: Permission denied
ls: cannot access 67705a.jpg: Permission denied
ls: cannot access 67705orig.jpg: Permission denied
ls: cannot access 67705t.jpg: Permission denied
-rw-r--r-- 1 apache apache  17897 May  9  2007 60001.jpg
-rw-r--r-- 1 apache apache  15096 May  9  2007 60001a.jpg
-rw-r--r-- 1 apache apache  36963 May  9  2007 60001orig.jpg

if I just do an ls -l, they show up like this:

-rw-r--r-- 1 apache apache  14174 May 25 11:52 65963t.jpg
-????????? ? ?      ?           ?            ? 67705.jpg
-????????? ? ?      ?           ?            ? 67705a.jpg
-????????? ? ?      ?           ?            ? 67705orig.jpg
-????????? ? ?      ?           ?            ? 67705t.jpg
-rw-r--r-- 1 apache apache  78527 Jun  5 12:00 70023.jpg

So I think I actually found it:
(and there may be a few other files like it)

I went into that directory, issued this command in one ssh session:

watch -d -n .3 'dmesg | tail -n 20'

Then in the other:

ls -l

I saw the new entries get added to dmesg/syslog everytime I ls -l'ed.

Any ideas what causes/caused this, and how I can fix it without fsck? I 
don't really care about these files, losing 4 jpgs isn't really so bad.

Michael

Mark Fasheh wrote:
> On Tue, Nov 13, 2007 at 05:43:03PM -0800, Michael Moody wrote:
>   
>> This occurs:
>>
>> pba1 / # echo 'locate <6733855010560701275>' | debugfs.ocfs2 -n /dev/sdd5
>> locate: Invalid block number - 6733855010560701275
>>     
>
> Ok, I messed up - that log prints the block number as read off disk, which
> is clearly wrong. Sorry.
>
>
>   
>> Also, if I unmount, and remount the nfs, should that fix it, or restart nfs 
>> services on the nodes themselves?
>>
>> Any idea why I see this on both of the nodes, where only the first node is 
>> exporting the filesystem via nfs?
>>     
>
> Hmm, if it's happening on the non-exported node then it's it might not be
> related to nfs.
>
> How big is this particular file system, in terms of # of inodes. If it's not
> a high number of files, you could just poke around from the shell and see if
> 'ls -l' within a directory reliably gives you that message.
>
> Also, you could run fsck.ocfs2 in offline, *readonly* mode and send a log...
> The problem with this is that it might give us tons of false positives :(
>
> fsck.ocfs2 -fn /dev/sdd5
>
> Be really really careful with that. Double check my command line via the man
> page to make sure that fsck won't try to modify your file system.
> 	--Mark
>
> --
> Mark Fasheh
> Senior Software Developer, Oracle
> mark.fasheh at oracle.com
>   

-- 

Michael S. Moody
Sr. Systems Engineer
Global Systems Consulting
Direct: (650) 265-4154
Web: http://www.GlobalSystemsConsulting.com

Engineering Support: support at gsc.cc
Billing Support: billing at gsc.cc
Customer Support Portal:  http://my.gsc.cc


NOTICE - This message contains privileged and confidential information intended only for the use of the addressee named above. If you are not the intended recipient of this message, you are hereby notified that you must not disseminate, copy or take any action in reliance on it. If you have received this message in error, please immediately notify Global Systems Consulting, its subsidiaries or associates. Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the view of Global Systems Consulting, its subsidiaries and associates.




More information about the Ocfs2-users mailing list