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; } } }

On the importance of running iwfsshrink after iwmigrate

nipper

Migrated a branch (6.7.2 to 7.1) 10 Editions or so, 5K files in the WA.

iwfsshrink output:

Files examined: 2707760
Bytes examined: 70174798602
Files found to be duplicates: 2654334

(not finished removing yet -only 2000 files removed about 3GB of 70GB total)

So of the 2.71 M files on my system, 2.65 M are dups.

Find more posts tagged with

Comments

Adam Stoller

Absolutely. It seems strange that the mere act or "replaying historical events" (which is what iwmigrate basically does) does not [seem to] utilize the same code that those same events do in terms of avoiding redundancy - but as it doesn't, I always advocate doing an iwfsshrink after iwmigrate - and then maybe one a quarter after that.

In terms of sharing some data (this was going from 6.5 to 6.7.2 SP2 + P1 on W2K3):

Not currently running.
Last started Wed May 12 07:32:54 2010
Last completed Wed May 12 16:26:47 2010
Files examined: 2312064
Bytes examined: 28436783391
Files found to be duplicates: 2280153
Files converted: 76931
Bytes removed: 23536484934