Kevin, Yes, that is just too old for vxattrs (the earliest tag with vxattr support in fuse is v0.57~84^2~6). In Ceph FS terms, 0.56 is pretty ancient. Because the filesystem is under active development, you should use a much more recent version for clusters with Ceph FS enabled -- at least firefly, and perhaps giant if you can tolerate a non-LTS release. John On Thu, Dec 18, 2014 at 12:08 AM, Kevin Shiah <aganwin@xxxxxxxxx> wrote: > Hi John, > > I am using 0.56.1. Could it be because data striping is not supported in > this version? > > Kevin > > On Wed Dec 17 2014 at 4:00:15 AM PST Wido den Hollander <wido@xxxxxxxx> > wrote: >> >> On 12/17/2014 12:35 PM, John Spray wrote: >> > On Wed, Dec 17, 2014 at 10:25 AM, Wido den Hollander <wido@xxxxxxxx> >> > wrote: >> >> I just tried something similar on Giant (0.87) and I saw this in the >> >> logs: >> >> >> >> parse_layout_vxattr name layout.pool value 'cephfs_svo' >> >> invalid data pool 3 >> >> reply request -22 >> >> >> >> I resolves the pool to a ID, but then it's unable to set it? >> > >> > Was the 'cephfs_svo' pool already added as a data pool with "ceph mds >> > add_data_pool"? >> > >> >> Ah, indeed. Working fine right now. Same goes for any other layout >> settings. >> >> > There are paths where if a pool was added very recently, MDSs/clients >> > might not know about the pool yet and can generate errors like this. >> > >> > John >> > >> >> >> -- >> Wido den Hollander >> 42on B.V. >> Ceph trainer and consultant >> >> Phone: +31 (0)20 700 9902 >> Skype: contact42on >> _______________________________________________ >> ceph-users mailing list >> ceph-users@xxxxxxxxxxxxxx >> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |