Scan stops without apparent reason

[pderwael]

Hi there

I'm in the process of relocating my mp3 collection from a win7+local & usb discs to a CentOS6.4+NAS

SS 4.8 (build 3434) - 17 avril 2013
Java: jetty-6.1.x, java 1.7.0_25, Linux (130,2 MB / 140,1 MB)
Running on CensOS 6.4 fully patched

The data is moved across, SS is installed, and running with 2MB RAM (--max-memory=2048)
The data is exported from the nas (CIFS read only) and mounted at /var/music
I have pointed SS at 29 directories under /var/music:
/var/music/0
/var/music/A
/var/music/B
/var/music/...
/var/music/Z
/var/music/~Ipod
/var/music/~Check

Started the media scan and everything seems ok until the scan progress (followed on /var/subsonic/subsonic.log) stops at
[2013-08-26 21:05:10,552] INFO MediaScannerService - Scanned media library with 142250 entries.
It should find +/- 400000 entries

"service subsonic stop" --> failed
"service subsonic status" --> subsonic dead but subsys locked

The web interface seems ok: I can play the music that has already been found, create playlists etc...
This is also true for music stored under ~Ipod & ~Check --> I don't think the "~" is the culprit
It seems that only the scan died...

Any clue gurus ??

[BKKKPewsey]

With that directory structure it should be easy to find where the problem is.
Making the assumption that the A folder contains artists starting with A etc then look at your already scanned music and find where the scan failed.
eg if you have all artists up to M with only a few M's then the likelihood is that something in the M folder is causing SS to trip up.
So disable the M folder from the scan and rescan - if the scan now completes then case is proven.
However finding the problem file(s) within the suspect directory not quite so easy

SS is installed, and running with 2MB RAM

Of course if that is trúe you may need to buy some more memory
(Hmm! SS running on a Sinclair spectrum - unusual )

[pderwael]

Thanks for the hint, I did not really suspect a corrupt file because the Windows version of SS is not crashing on the same directory structure and files
I have currently switched back to the Windows version of SS which is running on my laptop

Anyhow, I will try to scan every single directory one by one... I know what I will do this evening

Concerning the 2MB story, it is not running on a Sinclair, but on a ZX80... remember this one
Now seriously, I have set the max memory limit of both Win & Linux versions to 2Mb, and this is enough on my Win7

[pderwael]

I'm having second thoughts...

Instead of spending hours (if not days) trying every single directory (+/- 30,000 equivalent CDs, you get the picture), is there no possibility to activate a debug mode ??
Ideally, the scan should throw up an exception when a corrupt file is found...
Alternatively, every file scanned should be reported

Any thought on this ?