Update- I still do not have access to the blogs.dir/1/files directory.
I have pin-pointed the error to the word/directory "files"
This has happened on all of my auto upgrades to 3.0 - but I did not have the issue in the RC1 & RC2 nightly builds that I was running before 3.0 was officially released.
If I put the file in the blogs.dir directory without any subdirectories then the file is accessible.
See here: http://hanover4square.org/wp-content/blogs.dir/4sqlogo.jpg
It is still fine here: http://hanover4square.org/wp-content/blogs.dir/1/4sqlogo.jpg
But if I move the same file to the files sub-directory within blogs.dir it is not accessible?
See here: http://hanover4square.org/wp-content/blogs.dir/1/files/4sqlogo.jpg
But if I create a sub-directory called file1 the file is accessible?
See here: http://hanover4square.org/wp-content/blogs.dir/1/file1/4sqlogo.jpg
To magically redirect it would be:
So the issue is with the word/directory "files"