iwmigrate scf_TruncateFile failed err=301

Hi, we're migration a backing store from Teamsite 6.5 (Solaris) to 7.3.1 (Linux). Everything works great except a few files that were Modified in workareas that didn't get copied over due to err=301.

Also, sometimes running iwmigrate with -w -only flag twice carries a few more files over (with the same err=301 error).

Has anyone ran into a similar situation before? We've done iwusermigrate and iwaccessmigrate accordingly to the KB article the support engineer has provided but can't seem to figure out why we get these errors?

By the way, we are using Mandatory Write Lock model and branch security is turned on in iw.cfg.

Thanks you,

Find more posts tagged with

Comments

nipper

Likely that will be a support question.

Did you run iwfsck before you did the migrate ?

Do you have a list of the files that failed ? How many ? Are they complete ?

Are they accessible form TeamSite ?

rteng

Likely that will be a support question.

Did you run iwfsck before you did the migrate ?

Do you have a list of the files that failed ? How many ? Are they complete ?

Are they accessible form TeamSite ?

Hi nipper, thanks for the reply. I did open a ticket about this last month and the ticket is rather moving very slowly... and because we have launched to production already I thought I seek some other alternatives.

I did run iwfsck against the old backing store mounted on the new Linux box for 3 straight days with tons of errors and according to the support engineer it's expected because the metadata representation is still the older version. I did not have a chance to iwfsck in the actual Solaris box due to time constrains.

I have a complete list of these files, basically I made a list of files that had these error and used a script to do a diff in between old & new backing store. Some workareas had a few files and some workareas had thousands of files that are different and most of them were attached to workflows. Of which I dropped in the Linux box because the migrated workflow store works but getting an error in the GUI (some java null pointer exception).

They are accessible by Teamsite and if I unlock all these files (in old & new backing store) and re-lock them with the iwts account in such that they are all locked by the same person, they will get migrated over.

Does this sound like some type of bug of the iwmigrate tool when Mandatory Write lock is used?

Thanks again,

rteng

Notice 7.3.2 is out and there is a JIRA ticket regarding iwmigrate

TS-15745 - wmigrate sometimes converts normal extended attributes to large extended attribute format

could this be related?

Adam Stoller

I did run iwfsck against the old backing store mounted on the new Linux box for 3 straight days with tons of errors and according to the support engineer it's expected because the metadata representation is still the older version. I did not have a chance to iwfsck in the actual Solaris box due to time constrains.

I'm a bit concerned about the above statement. The steps I recommend doing are:

There may be some additional steps scattered in amongst the above, but that's generally the process I've used in numerous upgrade being performed between distinct servers.

nipper

I did run iwfsck against the old backing store mounted on the new Linux box for 3 straight days with tons of errors and according to the support engineer it's expected because the metadata representation is still the older version. I did not have a chance to iwfsck in the actual Solaris box due to time constrains.

This is why you are supposed to do the iwfsck BEFORE you copy it over. Whether these errors are expected or not, I will have to defer to the support engineer. Like Adam, I am concerned, but...

I have a complete list of these files, basically I made a list of files that had these error and used a script to do a diff in between old & new backing store. Some workareas had a few files and some workareas had thousands of files that are different and most of them were attached to workflows. Of which I dropped in the Linux box because the migrated workflow store works but getting an error in the GUI (some java null pointer exception).

Migrating workflows over seldom makes sense. I always make certain there are few if any active workflows.

They are accessible by Teamsite and if I unlock all these files (in old & new backing store) and re-lock them with the iwts account in such that they are all locked by the same person, they will get migrated over.

Does this sound like some type of bug of the iwmigrate tool when Mandatory Write lock is used?

Thanks again,

Maybe, I have never used Mandatory write locks. But it sounds like you have a workaround, remove all the workflows and locks. Then migrate.

Besides the error, is there a problem with the workaround ?