Minidlna is not collecting all media files.

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Enable media server in firmware 3.0.3.1-027
2. Rescan all media
3. Check if all media files are collected

Not all files are collected, some files are not included,
instead in the log we can see warnings:

"[2012/11/28 22:23:06] scanner.c:733: warn: Scanning /media/My_Disk
[2012/11/28 23:51:16] metadata.c:741: warn: Opening 
/media/My_Disk/Video/yyyyr.mkv failed!
[2012/11/28 23:51:16] scanner.c:505: warn: Unsuccessful getting details for 
/media/My_Disk/Video/yyyy.mkv!
[2012/11/28 23:51:40] metadata.c:741: warn: Opening 
/media/My_Disk/Video/xxxx.mkv failed!
[2012/11/28 23:51:40] scanner.c:505: warn: Unsuccessful getting details for 
/media/My_Disk/Video/xxxx.mkv!"

I'm running currently 3.0.3.1-027 firmware on RT-N56U, Linux Xubuntu 12.10.

The problem occured also on firmwares prior to 3.0.3.1-025.
particulary on 3.0.3.0-025 all files were scanned correctly !!!
In 1-026 changelog I can see that:

"- Rolled back package ffmpeg to v0.6.6. All new ffmpeg  branches > 0.6.x
  raise Page Allocation Failure during Minidlna scan ton media files."

Well this never happened to me (over 6000 files) on 3.0.3.0-025.
Could this can be fixed and more recent ffmpeg branch can be used instead ?

Is the issue with page allocation failure in 3.0.3.0-025 and media scanning is 
related to low memory ? Was it tested with active swap partiton ?

Kind regards

Artur

PS. Anyway despite some small bugs it is still awesome job guys !!!

Original issue reported on code.google.com by Artur.Sz...@gmail.com on 29 Nov 2012 at 4:09

[GoogleCodeExporter]

parsing files with ffmpeg-0.11.x work better, but all ffmpeg branches > 0.6 
really used more RAM and parsing some mediafiles raise Page Allocation Failure 
and system is crashed. minidlna + ffmpeg + sqlite is very difficult application 
for router. This is marketing bullshit. Router - is not NAS.  

Original comment by andy.pad...@gmail.com on 9 Dec 2012 at 3:02

[GoogleCodeExporter]

Thank you for explanation, 

however I still have some questions:

- with ffmpeg-0.11.x crash happens due to low memory or scanned file media type 
?

As I said before I have a swap active so on 3.0.3.0-025 nor any one crash 
happened
while some media files are larger then 10 GB, and the number of files is quite 
big. 

Is there any way to download 3.0.3-025 (I deleted it accidentally from my hdd) 
? 

Original comment by Artur.Sz...@gmail.com on 9 Dec 2012 at 4:32

[GoogleCodeExporter]

No, ffmpeg crashed on parse some specific media files, filesize is not matter.  
 Kernel invoked OOM Killer and result is bad.

Original comment by andy.pad...@gmail.com on 9 Dec 2012 at 6:48

[GoogleCodeExporter]

Thank you for the explanation.
In my setup it never happened but I understand why you have to roll back.
If you anyway keep somewhere the 3.03-025 version I will be grateful for a 
download link to this version. Still I would like to use it.

I think anyway the bug can be closed. 

Original comment by Artur.Sz...@gmail.com on 9 Dec 2012 at 7:07

[GoogleCodeExporter]

Original comment by d...@soulblader.com on 9 Dec 2012 at 9:31

• Changed state: WontFix