[Gluster-users] should be: gluster 3.31b*2* destroying mountpoints?

[Harry Mangalam]

Thanks for the zippy reply, Brian.

There seems to be a typo in your example - what does 'chmod foo/bar' 
supposed to do?

But even if that's the case, and the dir is not 'destroyed'.  Perhaps  
'made unusable' is a better description.  Is this the intended effect?

I assume not, but what could lead to it?  Or rather why should trying 
to mount a gluster volume lead to that effect?

hjm


On Thursday 22 March 2012 14:05:25 Brian Candler wrote:
> On Thu, Mar 22, 2012 at 01:56:49PM -0700, Harry Mangalam wrote:
> >    Previous email had a typo in Subject line.
> 
> What do you mean by "destroying" the mountpoint?
> 
> I have seen those d??????????? entries before (not with gluster).
> IIRC it's when a directory has 'read' but not 'execute' bits set.
> 
> $ mkdir foo
> $ chmod foo/bar
> $ chmod 666 foo
> $ ls -l foo
> ls: cannot access foo/bar: Permission denied
> total 0
> -????????? ? ? ? ?                ? bar

-- 
Harry Mangalam - Research Computing, OIT, Rm 225 MSTB, UC Irvine
[ZOT 2225] / 92697  Google Voice Multiplexer: (949) 478-4487
415 South Circle View Dr, Irvine, CA, 92697 [shipping]
MSTB Lat/Long: (33.642025,-117.844414) (paste into Google Maps)
--
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20120322/25afdef1/attachment.html>