INFplus

TAPs für die SRP- und CRP-Serie
Benutzeravatar
macfan
Ex-iTiNa-Promoter
Ex-iTiNa-Promoter
Beiträge: 24186
Registriert: Fr 9. Dez 2005, 10:16

AW: INFplus

#221

Beitrag von macfan »

INFplus often shows the information for another recording on my hard disk, sometimes even for a deleted recording. Have you any ideas? Does INFplus use hashing?

Gruß, Horst
TAP-Autostart SRP 2100: Automove - BackupSettings - dbFit - FastSkip - MediaAspect - Nice Display - PowerRestore - QuickPlay - ResetCAM - SmartEPG TMS - SmartFiler - StPBTools - TMSRemote - TimerDiags - TMA1 - V!deotext
TAP-Autostart 5k: TF5000 Display 1.53 - BootMenu 0.32
Davon gestartet: iTiNa 1.05 - ImproBox 2.5 - Stirf 1.3 BetaD (asrael) - Filer 2.30
DeltaMikeCharlie
WebController
WebController
Beiträge: 442
Registriert: Di 7. Mai 2013, 05:11

AW: INFplus

#222

Beitrag von DeltaMikeCharlie »

  1. What version of INFplus are you using?
  2. Does this problem appear with new recordings or just old recordings?
  3. How frequently does this problem occur?
INFplus does not use hashing. INFplus finds the inode of the INF file for the recording and then stores the additional EPG data in a file named using a zero-padded inode + .INF+ format (see example below).

In order to detect when recordings have been deleted, INFplus also makes hard links to the original INF file and uses the same zero-padded file name + .INF format.

Some time ago, FireFird discovered a bug in the SRP firmware that meant the link() function used to create the hard links on the HDD did not work correctly. This meant that the INF files for deleted recordings were not being detected correctly and the orphaned INF+ files were not being deleted. If the INF of a new recording received the inode of a deleted recording, then the INF+ file would contain data from the deleted recording as well as the new recording.

From INFplus version 1.1d onwards, a workaround was implemented for this firmware bug. Australian PVRs did not appear to have this firmware bug.

If the inode for the INF of a recording is "1234", then in "/ProgramFiles/Settings/INFplus", you should find the following files: 0000001234.INF and 0000001234.INF+.

To see the inode, telnet to the PVR, change into the INFplus directory and use "ls -laFi". This will also show you the link count.

Code: Alles auswählen

# ls -laFi
  [color=Blue]28777 [/color]drw-r--r--    3 root     root         4096 Jan  1 00:07 ./
  [color=Blue]28768 [/color]drw-r--r--   28 root     root         4096 Jan  1  2000 ../
   [color=Blue]1234 [/color]-rw-rw-rw-    [color=Red]2[/color] root     root         3320 May  3  2015 0000001234.INF
  [color=Blue]28781 [/color]-rw-rw-rw-    [color=Red]1[/color] root     root        53352 Jan  1  2000 0000001234.INF+
Any INF file with only 1 link has experienced the problem caused by the firmware bug and can be removed. An INF file with 2 links represents a recording that is still on the PVR and has not yet been deleted.

If you are using a recent version of INFplus, and the error is still occurring on new recordings, please send me a sample copy of the INF+ file for that recording via PM.
Zuletzt geändert von DeltaMikeCharlie am Mi 3. Jun 2015, 00:02, insgesamt 1-mal geändert.
Antworten

Zurück zu „SRP/CRP TAP-Bereich“