I think it should be: Path="test3" so without the initial '/'. Buckets aren't paths, we're just abusing the existing Ganesha config to select them. Other than that, the client entry should match the equivalent entry in your ceph.conf. Daniel On 04/26/2018 01:52 AM, Marc Roos wrote:
I have problems exporting a bucket that really does exist. I have tried Path = "/test:test3"; Path = "/test3"; Results in ganesha fails to start with message ExportId=301 Path=/test:test3 FSAL_ERROR=(Invalid object type,0)
If I use path=/ I can mount something but that is a empty export, but cannot put files there.
I have this in ganesha (client.rwg3 works with civetweb), should be sufficient not?
RGW { cluster = "ceph"; name = "client.rgw3"; ceph_conf = "/etc/ceph/ceph.conf"; # for vstart cluster, name = "client.admin" #init_args = "-d --debug-rgw=16"; }
EXPORT { Export_ID=301; Path = "/test3"; Pseudo = "/rgwtester";
FSAL { Name = RGW; User_Id = "test$tester1"; Access_Key_Id ="sameass3"; Secret_Access_Key = "sameass3"; } Disable_ACL = FALSE; CLIENT { Clients = 192.168.x.0/24; } }
[@~]$ s3cmd -c .s3cfg.tester1 ls 2018-01-31 21:48 s3://test 2018-02-01 11:44 s3://test2 2018-02-02 17:10 s3://test3
[@~]$ s3cmd -c .s3cfg.tester1 ls s3://test3 2018-02-02 17:13 10485760 s3://test3/10MB.txt 2018-02-05 12:57 26784 s3://test3/aB8q5BA_460s.jpg
[@ ganesha]# rpm -qa | grep ganesh nfs-ganesha-xfs-2.5.5-.el7.x86_64 nfs-ganesha-2.5.5-.el7.x86_64 nfs-ganesha-rgw-2.5.5-.el7.x86_64 nfs-ganesha-ceph-2.5.5-.el7.x86_64 nfs-ganesha-vfs-2.5.5-.el7.x86_64 nfs-ganesha-mem-2.5.5-.el7.x86_64
On CentOS7 _______________________________________________ Support mailing list -- support@lists.nfs-ganesha.org To unsubscribe send an email to support-leave@lists.nfs-ganesha.org