Great thanks. --Scott
On Fri, Jun 3, 2016 at 8:59 AM John Spray <jsp...@redhat.com> wrote: > On Fri, Jun 3, 2016 at 4:49 PM, Scottix <scot...@gmail.com> wrote: > > Is there anyway to check what it is currently using? > > Since Firefly, the MDS rewrites TMAPs to OMAPs whenever a directory is > updated, so a pre-firefly filesystem might already be all OMAPs, or > might still have some TMAPs -- there's no way to know without scanning > the whole system. > > If you're think you might have used a pre-firefly version to create > the filesystem, then run the tool: if there aren't any TMAPs in the > system it'll be a no-op. > > John > > > Best, > > Scott > > > > On Fri, Jun 3, 2016 at 4:26 AM John Spray <jsp...@redhat.com> wrote: > >> > >> Hi, > >> > >> If you do not have a CephFS filesystem that was created with a Ceph > >> version older than Firefly, then you can ignore this message. > >> > >> If you have such a filesystem, you need to run a special command at > >> some point while you are using Jewel, but before upgrading to future > >> versions. Please see the documentation here: > >> http://docs.ceph.com/docs/jewel/cephfs/upgrading/ > >> > >> In Kraken, we are removing all the code that handled legacy TMAP > >> objects, so this is something you need to take care of during the > >> Jewel lifetime. > >> > >> Thanks, > >> John > >> _______________________________________________ > >> ceph-users mailing list > >> ceph-users@lists.ceph.com > >> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com >
_______________________________________________ ceph-users mailing list ceph-users@lists.ceph.com http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
