On Wed, Jul 12, 2017 at 09:29:54AM -0700, Darrick J. Wong wrote: > > Might this be userspace not catching up to the various reflink > > and co updates? > > Hmm, I'll have a look at that. > > FWIW I'm half wondering if it's worth it to keep running xfs_check, > since it occasionally bombs out with ENOMEM (xfs_repair reports no > problems). When I started working on reflink I had to update xfs_db > to support v5 at all, which made me wonder if anyone was testing v5. Yeah, it might be better to drop it. > > xfs/293 complains about undcoumented xfs_io commandsa: > > > > +cowextsize not documented in the xfs_io manpage > > +dedupe not documented in the xfs_io manpage > > +finsert not documented in the xfs_io manpage > > +fsmap not documented in the xfs_io manpage > > +funshare not documented in the xfs_io manpage > > Works for me... but then I delibrately bindmount my dev tree's > xfs_io.8.gz to the appropriate place in /usr/share/man/ before running > xfstests. ;) I just did a make install of the latest xfsprogs before the run. -- To unsubscribe from this list: send the line "unsubscribe linux-xfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
