On Wed, Apr 12, 2017 at 02:32:02PM +0200, David Sterba wrote: > On Wed, Apr 12, 2017 at 09:35:00AM +0800, Qu Wenruo wrote: > > > > > > At 04/12/2017 09:27 AM, Liu Bo wrote: > > > A typical use case of 'btrfs-map-logical' is to translate btrfs logical > > > address to physical address on each disk. > > > > Could we avoid usage of btrfs-map-logical here? > > Agreed. > > > I understand that we need to do corruption so that we can test if the > > repair works, but I'm not sure if the output format will change, or if > > the program will get replace by "btrfs inspect-internal" group. > > In the long-term it will be repleaced, but there's no ETA. Possibly, if fstests maintainer agrees, we can add btrfs-map-logical to fstests. It's small and uses headers from libbtrfs, so this would become a new dependency but I believe is still bearable. I'm not sure if we should export all debuging functionality in 'btrfs' as this is typically something that a user will never want, not even in the emergency environments. There's an overlap in the information to be exported but I'd be more inclined to satisfy user needs than testsuite needs. So an independent tool would give us more freedom on both sides. -- To unsubscribe from this list: send the line "unsubscribe fstests" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
