On Fri, Feb 02, 2018 at 04:45:33PM -0500, Todd Gill wrote: > > Hi, > > I'd like to be able to take a snapshot of an XFS filesystem on top of > dm-thin. > > The goal for the snapshot is: > > - fast to complete (couple seconds or better) > - independent of origin (UUID updated?) > - read/write > > To satisfy the independent goal, I'm updating the UUID on the snapshot. > Currently "xfs_admin -U xxx" takes in the ballpark of 14 seconds on my > test system. There's a very good chance that this is caused by dm-thinp doing COW for the storage underlying the superblocks modified by the UUID change. Best to start by measuring how much IO is going on when you change the UUID. e.g. `iostat -x -d -m 1`. An strace showing how long the xfs_db read() and write() calls to the dm-thinp device would lso be instructive. > Is there a better approach to achieve the goals? No, you are doing the right thing. > Or can the UUID update > be changed to be faster? Not sure - there's a fixed amount of modification we need to make to change the UUID so I'm not sure there is any optimisations we can make here. If it's the speed of the underlying snapshot device doing COW after a snapshot that is causing this issue, then there's probably nothing we can do about it at the filesystem layer, anyway.... Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx -- 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
