[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

RE: [Linux-cluster] Strange directory listing

> -----Original Message-----
> From: linux-cluster-bounces redhat com 
> [mailto:linux-cluster-bounces redhat com] On Behalf Of Bob Peterson
> Sent: Friday, March 06, 2009 8:47 AM
> To: linux clustering
> Subject: Re: [Linux-cluster] Strange directory listing
> ----- "Jeff Sturm" <jeff sturm eprize com> wrote:
> | We keep Lucene search indexes on a GFS storage volume, mounted 
> | cluster-wide. This way each cluster node can perform a search, or 
> | append the search index with new content. Works great.
> | 
> | Funny thing is, when I list the directory containing the 
> search index, 
> | I sometimes see output like the following:
> | 
> | $ ls -l
> | total 600
> | ?--------- ? ? ? ? ? _2931.f3
> What level of GFS driver is this?  Are you up2date or running 
> a recent level?

We aren't running Red Hat.  We have:

CentOS release 5.2 (Final)

> The thing to do is "stat 
> _2931.f3" on all nodes in the cluster and see if the "Inode" 
> value is the same on all nodes.

The rogue files don't stay around long enough to stat() on all nodes.
My assumption is that these are files just created or in the process of
being destroyed, and I don't see them in two successive "ls -l"

I wasn't too concerned since this doesn't seem to have any negative
impact on the application, but was curious nonetheless.



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]