iwfsshrink Not currently running / Operation already in progress

Crsb

I am trying to run iwfsshrink on a 50GB default store with large number of duplicate files (across branches) and large number of submitted ( about 450000 hidden edition).

I invoked this cmd "iwfsshrink run default" 4 days ago, then i tried "iwfsshrink status default" and i got "Not currently running. Last started Mon May 7 23:13:54 2009 Last completed Tue May 8 00:28:04 2009...", i assumed maybe because i just invoked the cmd and it will take while before it returns any stats. i tried the next day and i got the same msg, it has been 4 days now and i am still getting the same status. i have tried to run it again (without abort) and i get "Operation already in progress:02440: Operation already in progress"...
i run the same thing on iwadmin store and i immediatly got the "phase 1 status.." then it finished within few minutes.
in iwtrace log, i can see msg "RemoveDuplicateData: Start Phase 1." when i run the cmd for iwadmin, but i dont seetthat msg when i run it for default.

Do you think i should just give it more time? or abort it and do something else?

This is on 672SP2/RH5, the entire iw-store was migrated from 671SP1, the store is running fine and no performance issues.

----
Something happened to the search on devnet, i couldn't get any results for "iwfsshrink" even i know it was mentioned endless times.

Adam Stoller

If two seconds (arbitrary number) after issuing the command:

iwfsshrink run default

you run

iwfsshrink status default

and it doesn't show it running - something is wrong.

I've never seen that happen, so I can't even begin to guess what's happening - unless you fat-fingered the original command (there are two "s"'s in iwfsshrink, maybe you missed one, though you should get an error about an unknown command in that case).

I'd suggest contacting support (despite recent rumblings of them being backlogged or such). While waiting (or perhaps just before) I'd suggest doing something like rebooting the box, making sure it comes up cleanly, and then try to run the same command(s) again and see what shows up.