If you get a “not a working copy” when doing a recursive svn cleanup, you likely have a subdirectory which should be a working copy (i.e. the .svn directory at the top level says so), but the subdirectory is missing its own .svn directory.
In that case, you could move or delete that directory and then do a local update. To delete the directory,
rm -rf content
svn checkout content
WARNING: rm -rf deletes the folder content permanently.
If you get a not a working copy error, it means that Subversion cannot find a proper .svn directory in the content subdirectory. Check to see if there is an .svn directory in content.
The ideal solution is a fresh checkout, if possible.