Reputation: 847
I have the following error while running the build in the dynamic view. It looks like an mvfs caching problem.
The build succeeded after I ran it few times but what might be the problem behind it?
pid/tid 900/938} cleartext lookup view= vob= dbid=0x80000173 - error 6
[2013/12/14 02:56:10.233] mvfs: Error: {858 pid/tid 900/938} cleartext pname= \Device\Mup\.......\.s\00030\8000017352aab277sc100-elf2xx.exe
[2013/12/14 02:56:18.603] mvfs: Error: {859 pid/tid 900/938} cleartext lookup view= vob= dbid=0x80000173 - error 6
[2013/12/14 02:56:18.603] mvfs: Error: {860 pid/tid 900/938} cleartext pname= \Device\Mup\.....\.s\00030\8000017352aab277sc100-elf2xx.exe
[2013/12/14 02:56:24.951] mvfs: Error: {861 pid/tid 900/938} mvfs_nt2vfs_opensendirp: failed OPEN irp fop 0xFFFFFA800EF21700 status 0xc000006d [2013/12/14 02:56:24.951] mvfs: Error: {862 pid/tid 900/938} DriverName: \FileSystem\FltMgr
[2013/12/14 02:56:24.951] mvfs: Error: {863 pid/tid 900/938} FileName: ....\.s\00030\8000011952aab271objcopy.exe
Upvotes: 1
Views: 800
Reputation: 1324347
Considering the objects which are troublesome in the private storage area (.s
) of the view storage are .exe
, it is possible it is linked to some kind of process keeping an handle on said exe, and preventing ClearCase to properly access them.
It is best to use two dynamic views: one for accessing data, and one for building data, in order to use one for read/access and execution, and the other for write access and compilation.
This old thread mentions restarting the albd_server service can help.
That is also akin to stopping / restarting the view (cleartool endview -server
).
Upvotes: 1