search for: lancelotd

Hi, I'm a bit curious of error messages of the type "remote operation failed: Stale NFS file handle". All clients using the file system use Gluster Native Client, so why should stale nfs file handle be reported? Regards, /jon -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi all, I am having problems with painfully slow directory listings on a freshly created replicated volume. The configuration is as follows: 2 nodes with 3 replicated drives each. The total volume capacity is 5.6T. We would like to expand the storage capacity much more, but first we need to figure this problem out. Soon after loading up about 100 MB of small files (about 300kb each), the

hi, all when I`m copying a file (about 1GB) into the volume, I tried to replace one brick of the volume. Then the copying was halted with the error msg: "cp: writing "./d", transport endpoint is not connected". Besides, I use two server bricks without afr. I`m not sure, is it a bug, or a yet-to-be-added feature of glusterfs? Best Regards. Jules Wang.