On Wed, Oct 3, 2018 at 3:47 PM Joe Thornber <thornber@xxxxxxxxxx> wrote: > > On Wed, Oct 03, 2018 at 03:13:36PM +0100, Thanos Makatos wrote: > > > Could you say more about why you want to do this? > > > > > > > So that I can directly read the data block without having to pass through > > dm-thin, e.g. there might be a more direct datapath to the physical block > > device. > > > > Mappings don't change if you're not using snapshots. If you are, then any > > > write > > > to a shared block will trigger a copy on write operation, and subsequently > > > a new > > > mapping. > > > > So for backups etc. I made the metadata snapshot available, which gives you > > > a > > > view of all the metadata frozen at a point in time. If you're using the > > > metadata > > > snap you still need to guarantee the mappings for the devices that you're > > > interested > > > in are not changing. eg, instead of backing up a live thin, take a > > > snapshot of the thin > > > and back this up instead. > > > > > > > For now I can guarantee that these mappings don't change (no snapshots, > > backups, etc), so it's safe to extract the mapping(s) without having > > acquired the meradata snapshot, correct? If this is the case, then how can > > I extract individual mappins? (Either from kernel space or from user > > space.) Are there specific dm-thin kernel functions I should start looking > > at? > > Why is this thin-specific? What happens if there are two thin-pools under > your code? Do you want the final physical location? The whole dm stack? You're right, this isn't thin-specific. Currently there will be only one thin pool per physical device so it's simple enough. Indeed I want the physical location, knowing the location in the data LV would suffice. >> Efficiently reading the metadata requires a cache of metadata blocks. Thinp uses dm-bufio > to provide this. It seems very wasteful for you to duplicate this. So your options are: > > > i) querying the pool metadata object directly. Currently there is no way to get hold of the > metadata object, you would need to make any queries off the io path, since they can block. Do you mean that the pool metadata object is internal to dm-thin so that other kernel modules cannot access it? If so then I suppose I can add functions do dm-thin that return an opaque pointer to it (or something like that). Is there some specific function that given the poo metadata object can return this information? I've started looking at thin_bio_map(), is this the best place to start? Also, is option (i) doable from userspace? Is there logic in thin_dump to access the on-disk metadata? I suppose I will have to take care when reading the metadata as they might not have been committed to disk. >> ii) or examining the completed bios, you'd probably need to add some per bio data to give context. I think option (ii) sounds like the most efficient one but most invasive. -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
