@mjjinvincible
Looking again at your extra long file path ....
Your http://domain.com/files/ bit should only refer to your site home blog (blog number 1) because in the url ...
-- http://domain.com/files/
is exactly the same as
-- home/content/username/html/wordpress/wp-content/blogs.dir/1/files/
in terms of location in your hosting space
this means your rewrite rule somewhere is "joining" the two paths, instead of "rewriting" the longer one to replace it with the shorter one.
In effect, it is using "http://domain.com/files/" in place of "http:" - notice the double "//" in the middle of your url?
What it should be doing is using "http://domain.com/files/" in place of "home/content/username/html/wordpress/wp-content/blogs.dir/1/files/"
Even that is not 100% accurate, but will give you a starting point to hunt it down ... what it should be doing depends on whether it is the site home blog, or a user blog.
For example with blog_ID=2 (call it lostsoul) ...
"home/content/username/html/wordpress/wp-content/blogs.dir/2/files/year/month/image.jpg"
should become, either -
http://lostsoul.domain.com/year/month/image.jpg
or
http://domain.com/lostsoul/year/month/image.jpg
... depending on if you use subdomain or subfolder user-blogs
The same file in your site's home blog would be ...
http:/domain.com/year/month/image.jpg
The /files/ folder should not be necessary in your path at all if it's set up correctly / efficiently ... unless you want it there because of using something like .../files/avatar.jpg outside of and above the year and month folder heirarchy?
losing the /files/ folder as part of the path would be my preference - just have to check if doing it would break anything though :-D
Gaz