iwfsck

Hi

How long does it take for iwfsck to complete? It took only less than 20 minutes to finish iwfsck. But it already took more than two days to run iwfsck -d -p -r and it is still running. Sounds too long to run it? Could any who has run iwfsck command to share how long it takes to finish their iwfsck commands? Thanks.

Regards,
civ3.

Find more posts tagged with

Comments

clogan

I ran iwfsck -d with TS 5.0.1 sp1 on Solaris 8 with a 37 gig backing store. I froze Teamsite Friday night, and it was still running Sunday night when I had to end it because our Australian users were ready to work.

Adam Stoller

There are a ton of variables involved here, like:

What version of TeamSite?
What platform?
What hardware is being used for the server
How big is the backing store?
Have you run iwfsshrink on the backing store?
etc.

At my current customer's site we had about 22 Gb backing store on a 5.0.2SP1 Solaris backing store and iwfsck -d would take about 2 hours (I don't know the specifics of the hardware but I believe it was at least 2-CPUs, possibly 4, with a RAID disk-array system). We converted the backing store to a 6.1 server (4 CPUs I'm pretty sure), ran iwfsshrink on it - resulting in a 9Gb backing store which took less than 1 hours to run iwfsck -d on it.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

clogan

Do you remember what was the size of the backing store before you ran iwfsshrink?

fish

I could be wrong but I think the number of Editions has a large effect on time to run iwfsck

Steve

Adam Stoller

As I said - the original backing store on 5.0.2 was about 22 Gb - after conversion the size of the backing store on 6.1 was about 32 Gb - after running iwfsshrink on the 6.1 store it was just under 9 Gb.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

clogan

Thanks for the info.

DaveDeutsch

Thought I'd share our experience in running this on a TS 5.5.2 dedicated unix server (SAN storage) with a 16GB backing store. To my knowledge we have never run iwfsck before in the 5-6 years we have been running TeamSite, nor have we run the shrink utility (though we don't delete much from TeamSite). We ran the following (we got the latest iwfsck inspite of running TS 5.5.2 upon the advice of our IWOV consultant):

Command line: /opt/iw-home/private/bin/iwfsck -d -p -r -nofmtchk
iwfsck: 6.7.0 Build 55985 Interwoven 20060321

Total points read: 67430679
Directories walked: 81960
Files walked: 288017
Symlinks walked: 0
TeamXML files walked: 0
Zombies walked: 14322
Total disk reads: 22555548
Total Run time: 152223 secs -> 1 Days 18 Hrs 17 Mins 3 Secs
Total Memory Usage: Process Size -> 398472 KB, Resident Size -> 395216 KB

Yes, you read that correctly: 42+ hours for a 16GB backing store. I read the earlier posts and looked for disk contention during this time but found none. The only curious statistic is the paging out of memory was much higher than normal.

Adam Stoller

Thought I'd share our experience in running this on a TS 5.5.2 dedicated unix server (SAN storage) with a 16GB backing store. To my knowledge we have never run iwfsck before in the 5-6 years we have been running TeamSite, nor have we run the shrink utility (though we don't delete much from TeamSite). We ran the following (we got the latest iwfsck inspite of running TS 5.5.2 upon the advice of our IWOV consultant):

Command line: /opt/iw-home/private/bin/iwfsck -d -p -r -nofmtchk
iwfsck: 6.7.0 Build 55985 Interwoven 20060321

Total points read: 67430679
Directories walked: 81960
Files walked: 288017
Symlinks walked: 0
TeamXML files walked: 0
Zombies walked: 14322
Total disk reads: 22555548
Total Run time: 152223 secs -> 1 Days 18 Hrs 17 Mins 3 Secs
Total Memory Usage: Process Size -> 398472 KB, Resident Size -> 395216 KB

Yes, you read that correctly: 42+ hours for a 16GB backing store. I read the earlier posts and looked for disk contention during this time but found none. The only curious statistic is the paging out of memory was much higher than normal.

If you had run the command with just the '-d' and not the '-p -r -nofmtchk' flags - it probably would have been faster. And unless they've changed their general recommendation - IWOV Support has always recommended that you run with just the '-d' flag until/unless a problem has been discovered and discussed with them.