On Thu, Sep 27, 2012 at 04:39:35AM -0700, Linda Walsh wrote:
> I want to be able to rapidly determine the diffs between 2 volumes.
> Special note 1 is an active lvm snapshot of the other -- meaning it is
> frozen in time, but otherwise should look identical the the file system
> as it was when it was snapped.
> Sooo... a way of speeding checks is finding out what blocks allocated to the
> are different, since as the new volume gets used, I had hoped that differing
> block numbers might give me a clue as to what had changed..
Differing block maps for the same inode on the two filesystems will give you a
clue that there are changes but it isn't perfect:
Consider xfs_fsr. This might change block numbers for a file but the contents
stayed the same.
Also consider an overwrite situation. The contents of the file are overwritten
and have changed but the block map stayed the same. To detect that we'd need
some kind of generation number on every extent, and we don't have that.
At this time I don't think we have a solid way to tell you which blocks of a
file are different without actually comparing them. I think you are stuck
looking at the mtime and then doing a full comparison.
Have you looked into using the xfs bulkstat ioctl interfaces?
XFS_IOC_FSBULKSTAT won't get you the block map, but maybe it would be useful to
you. xfs_bmap is using XFS_IOC_GETBMAP*, but it sounds like you've already
considered that. Maybe a creative invocation of xfsdump?
Let me know if I misunderstood and went off the rails. ;)
> Nevertheless, trying to read the blocks allocated/inode with bmap is sorta
> I've tried to optimize it by starting a pty session to xfs_db and issuing
> commands -- but I have to wait for a prompt to come back to know that the
> has finished, and I'm not really sure it's really returning more than 1 line
> for any file. -- though interactively, I can find a file with a large ACL,
> and see
> it has both a data and attr bmap. I also haven't seen what output would look
> if the file(or dir) was split -- as, so far, have only seen
> files/dirs returned that
> have 1 allocation/file,
> So what the means is that I'm not sure about synchronization between commands
> and the input I read in -- even though I read in the input after
> every command. -- but even with
> a minimal timeout of 1ms, and keeping track of commands outstanding
> and replies (as measured
> by 'prompts' recieved, I'm far from convinced it's doing the right
> thing -- and it still
> slow going 1 inode at a time over a pty interface.
> I thought of trying to use blockget -v and parsing the output. I
> figured that would
> have the least latency and likely be the fastest way to dump the mappings --
> it seems I can't get it to work on an active file system. So how
> can I get that block
> info dumped without blockget? I've already told blockget it's in -r
> only mode... so it
> shouldn't try to repair inconsistencies...and 99.999% is going to be
> what I want and any
> inconsistencies, I can check manually be checking the files through
> the mounted interface.
> Oddly, and likely I'm confused about something, but when i try to
> print the log/log_print,
> it says it is an invalid log 1 byte long, so even if it were played out, I
> think it would make much difference in the final results.
> Is it possible to do what I want w/o writing a special util/C prog to dump
> xfs mailing list