q content damaged=yes shows nothing also, just as q content showed nothing.

Is it possible, that since I had deduplication turned on, it turned
the files into chunks and it has way more chunks obviously than files,
and that's why it's taking so long?  I never got any deduplication,
because the data never moved through reclamation or migration, but it
might have still broken it up into chunks and stored extra DB entries
for that.

On Wed, May 12, 2010 at 5:44 AM, Richard Sims <rbs AT bu DOT edu> wrote:
> You probably have database damage, which can result from running the server 
> without the safeguards recommended in the Admin Guide manual.  Running Query 
> CONtent ... DAmaged=Yes on the volume may reveal the files in trouble.
>
>   Richard Sims   http://people.bu.edu/rbs/
>



-- 
Andy Carlson
---------------------------------------------------------------------------
Gamecube:$150,PSO:$50,Broadband Adapter: $35, Hunters License: $8.95/month,
The feeling of seeing the red box with the item you want in it:Priceless.