Skip to main content

IFS Errors

5 replies [Last post]
rdecker
Offline
Joined: 2009-02-25
Points: 0

While these errors aren't causing any issue I can see maybe they are of interest to whoever is working on this code. I am using HDHR. It seems there is a cache of the stream being stored and at some point it loops to delete the first file. There are 14 file pairs (mpg+ndx) that span over 2 hours. The last one is current time. I believe I started the RI about about 2 hours ago.

20100929 14:09:15.903 ERROR RI.IFS- IfsReturnCodeFileDeletingError: remove(C:
/CableLabs/tru2way/tags-RI_I1_1_4_REL_C-10708/ocap-ri/ocap/bin/CableLabs/simulat
or/Win32/debug/env/storage/I1/TSB/4CA36700_0029/0000000001.mpg) failed (13) in l
ine 1552 of IfsImpl.c
20100929 14:09:15.905 ERROR RI.IFS- IfsReturnCodeFileDeletingError: remove(C:
/CableLabs/tru2way/tags-RI_I1_1_4_REL_C-10708/ocap-ri/ocap/bin/CableLabs/simulat
or/Win32/debug/env/storage/I1/TSB/4CA36700_0029/0000000001.ndx) failed (13) in l
ine 1559 of IfsImpl.c
20100929 14:09:15.907 ERROR RI.GStreamer- gstindexingfilesink.c gst_file_sink
_render:712 gst_file_sink_render() IfsWrite is bad: File Deleting Error

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
mkorzen
Offline
Joined: 2008-03-05
Points: 0

This problem has been fixed on trunk in rev. 10753.

laurentiud
Offline
Joined: 2010-10-22
Points: 0

The fix is for IfsWrite. Does it fix a similar problem in IfsStop as well?

mkorzen
Offline
Joined: 2008-03-05
Points: 0

The actual fix consisted of multiple check-ins addressing different sub-problems. To answer your question though, one of the problems was with the function GetCurrentFileParameters which left some file handles opened as a side-effect of querying the physical file parameters. High-level functions that were affected by this were IfsWrite, IfsHandleInfo and IfsStop.

laurentiud
Offline
Joined: 2010-10-22
Points: 0

Thank you for your reply.

greg80303
Offline
Joined: 2008-07-03
Points: 0

We have actually been tracking this issue for quite a while now internally. We have just (in the last week) identified the problem. We plan to have the fix fully ready for the RelD release.

G