nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

iwfsck run times

System

Just starting a new thread to report run times of iwfsck as there seems to be periodic interest in this topic.

iwfsck -d -b

Server:
Quad 3.0 GHz CPU w/ Hyperthreading
8 Gb RAM

8.5 Gb / 12.7 Gb on Disk : 2 Hrs 45 Mins 58 Secs
Approx: 3 Gb / Hour (4.6 Gb / Hour if you use "on disk" size)
14.8 Gb / 20.8 Gb on Disk: 6 Hrs 38 Mins 52 Secs
Approx: 2.2 Gb / Hour (3.1 Gb / Hour if you use "on disk" size)

Note: Running iwfsck -**** -d -b gives "infinite" run time on the same backing store. Verbosity level (-**** option) is not just output, it actually affects what the process does.

On disk size will vary depending on the block size you have formatted your volume with.

Find more posts tagged with

Comments

Adam Stoller

Just starting a new thread to report run times of iwfsck as there seems to be periodic interest in this topic.

iwfsck -d -b

Server:
Quad 3.0 GHz CPU w/ Hyperthreading
8 Gb RAM

8.5 Gb / 12.7 Gb on Disk : 2 Hrs 45 Mins 58 Secs
Approx: 3 Gb / Hour (4.6 Gb / Hour if you use "on disk" size)
14.8 Gb / 20.8 Gb on Disk: 6 Hrs 38 Mins 52 Secs
Approx: 2.2 Gb / Hour (3.1 Gb / Hour if you use "on disk" size)

Note: Running iwfsck -**** -d -b gives "infinite" run time on the same backing store. Verbosity level (-**** option) is not just output, it actually affects what the process does.

On disk size will vary depending on the block size you have formatted your volume with.

You also have to factor in the average size of the files in your backing store the amount of metadata, and I believe the average number of file revisions

GeoffD

This certainly doesn't bode well for my plan to run iwfsck on my 200GB store this weekend

Adam Stoller

This certainly doesn't bode well for my plan to run iwfsck on my 200GB store this weekend

Start it Friday evening, making sure that the output is captured in a log file and that nothing is scheduled that would interrupt the process - and then try to check it a few times over the weekend (like morning and evening Saturday and Sunday) - and if you're lucky - it will be done Monday morning ;-)

It would be interesting to know:

Also - is this a production or development backing store (I imagine it's production) - if you have a development machine with the same version of TS, and sufficient space to put a good copy of the production backing store there, you can run the iwfsck on your dev box instead of production ...

GeoffD

As you guessed, this IS the Production version. Luckily, we recently built a Disaster Recovery Server, so worst-case scenario, I can just copy the store to that server and run it at my leisure.
I'm going to be running an iwshrink first just to see how much I can reduce the store by before I try anything else. In retrospect, I probably should have done that last night.
I'll update on Monday with my progress (and specs).

GeoffD

Well it didn't go as well as we hoped. I was unable to run anything other than a iwfsck -d (any other command ran 4-6 hours before an "insufficient memory" error).

We're now going to have the weekend backup restored to our other server so we can work on it uninterrupted.

Anyway, here are the server specs:

W2K3 server
Quad 3.0 GHz CPU w/ Hyperthreading
6 Gb RAM

Adam Stoller

Good luck - keep us posted.
You might also contact IWOV Support and see if they have any suggestions for reducing the memory footprint of the process (note: in general '-d' is the only flag you should use unless instructed otherwise by support)

GeoffD

We have finally had the production content (iw-store) restored to our backup server. Since the servers have different names, the SID is showing up as a number. Should I expect any issues with this when I run iwfsck?

Adam Stoller

We have finally had the production content (iw-store) restored to our backup server. Since the servers have different names, the SID is showing up as a number. Should I expect any issues with this when I run iwfsck?

I don't think that iwfsck will care about the SID's (feel free to double-check with Support) - I think that only matters if you're attempting to use the copy of the backing store on that server.

Frederik

Well it didn't go as well as we hoped. I was unable to run anything other than a iwfsck -d (any other command ran 4-6 hours before an "insufficient memory" error).

We're now going to have the weekend backup restored to our other server so we can work on it uninterrupted.

out of curiosity, how did this story continue?

btw, isn't there a -s flag that keeps memory use under control (but runs slower)

Frederik

FWIW, I just did a few iwfsck runs as part of the restore test on a store backup.

This is on 4 yr old Sun hardware, 2 CPU, 2GB. TeamSite 6.5 sp2 + all patches.

Store = 2.6 GB, started 8 months ago, has some 2000+ DCRs, and some 4000 generated HTML pages, and 1000 binary files (pdf, img, ...). Some HTML pages have many versions (regen'd between 1-100 times a day). Also between 1-100 editions published per day, which are (all but one) deleted after a week.

I'm rather surprised at how quick this went...

iwfsck -d -b $DIR
Total points read: 861324
Directories walked: 34029
Files walked: 24530
Zombies walked: 247
Total disk reads: 73454
Total Run time: 40 secs -> 40 Secs
Total Memory Usage: Process Size -> 72448 KB, Resident Size -> 68680 KB


iwfsck -d -s -b $DIR
Total points read: 7265807
Directories walked: 94434
Files walked: 3716140
Zombies walked: 49939
Total disk reads: 4846867
Total Run time: 1408 secs -> 23 Mins 28 Secs
Total Memory Usage: Process Size -> 19608 KB, Resident Size -> 17608 KB

iwfsck -d -r -b $DIR
Total points read: 982982
Directories walked: 34029
Files walked: 24530
Zombies walked: 247
Total disk reads: 88975
Total Run time: 38 secs -> 38 Secs
Total Memory Usage: Process Size -> 73976 KB, Resident Size -> 69888 KB

iwfsck -d -r -p -b $DIR
Total points read: 1841774
Directories walked: 34029
Files walked: 24530
Zombies walked: 247
Total disk reads: 107453
Total Run time: 485 secs -> 8 Mins 5 Secs
Total Memory Usage: Process Size -> 333104 KB, Resident Size -> 331208 KB

iwfsck -d -r -p -s -b $DIR
Total points read: 67138934
Directories walked: 94434
Files walked: 3716140
Zombies walked: 49939
Total disk reads: 11133827
Total Run time: 6959 secs -> 1 Hrs 55 Mins 59 Secs
Total Memory Usage: Process Size -> 24296 KB, Resident Size -> 22456 KB

For each run, I removed the following from the output, for shortness

Symlinks walked: 0
TeamXML files walked: 0
FINISHED 0 error(s) found