Re: file shown by ls but inaccessible (dht confusion?)

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

 



On Wed, Jul 27, 2011 at 05:06:33AM +0000, Emmanuel Dreyfus wrote:
> client# ls /gfs/usr/src/tools/compat/obj/ |grep strlcat.lo
> strlcat.lo
> client# ls /gfs/usr/src/tools/compat/obj/strlcat.lo
> ls: /gfs/usr/src/tools/compat/obj/strlcat.lo: Socket is not connected
(...)
> The "Socket is not connected" message is there because one of the servers
> is down. That should work anyway, right?

Wrong: the thing heals as soon as the other server is up again. Is this
something expected?

-- 
Emmanuel Dreyfus
manu@xxxxxxxxxx



[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux