Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am trying to test run Gluster with a volume consisting of two local bricks, the first being a plain directory and the second being a s3ql based mount.

Having just the plain directory as a unique brick works fine.

Having just the s3ql mount as a brick does not work:

drwxr-xr-x.  4 root root 4096 May 13 19:57 .
dr-xr-xr-x. 22 root root 4096 May 13 18:25 ..
d??????????  ? ?    ?       ?            ? gluster_testdir

Having both bricks added only the space of the first brick is showed as available, plus nothing can be written or read from the volume.

I am not sure if it does not work because Gluster is trying to re-mount (mount an existing non-local mount) the s3ql mount or because Gluster does not see the s3ql mount as a "real" directory even though it should.

Any hints?

share|improve this question
s3backer actually works fine as a gluster brick. But why not s3ql? – mr-euro May 14 '12 at 12:12
I think it may be the filesystem type: s3backer's loop device is recognised as ext4 while s3ql as another fuse system (fuse.s3ql). – mr-euro May 17 '12 at 12:00

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.