No subject

       It runs for up to two hours after which it records the
       filesystem where it left off, so it can start there the next
       time.  This  information  is stored in the file
       /var/tmp/.fsrlast_xfs.  If the information found here is somehow
       inconsistent or out of date it is ignored and reorganization
       starts at the beginning of the first filesystem found in
       /etc/mtab.

If xfs_fsr stopped at 2 hours, multiple additional runs will likely be
required to get good defragmentation.

> xfs_db and got the following results:
> 
> $ sudo xfs_db -c frag -r /dev/mapper/appl_vg-appl_lv

The -r above suggests you created a large realtime section for your
MythTV storage.  It may be helpful for you to provide xfs_info output
for the heavily fragmented filesystem.

> invalid numrecs (27111) in bmapbtd block
> invalid numrecs (4716) in bmapbtd block
> invalid numrecs (58978) in bmapbtd block

I'll leave these errors for one of the devs to tackle.

> actual 1034793, ideal 11024, fragmentation factor 98.93%
> 
> The fragmentation level was reduced, 

It was likely reduced much more than this.  Dropping caches or
unmounting and remounting the filesystem is often necessary after
running xfs_fsr in order to show the actual fragmentation level.  Try:

# echo 3 > /proc/sys/vm/drop_caches

and then run xfs_db again.

> but I was concerned about the error
> messages.  Before I go any further, am I corrupting my file system with the
> defragging or are these "invalid numrecs" messages unimportant?

Run 'xfs_check' or 'xfs_repair -n' and post the results.

-- 
Stan