Bug: Occasionally I’ll run into an episode that won’t import because of the season number having a leading 0 (S010E##, with Season 10 having a 0 preceding making it S010). Once I get rid of the trailing 0, it imports fine.
Bug: My ZFS volumes down’t show up under “Disk Space” in the system tab. They are there under a standard ‘df -h’ command though.
Debian wheezy under Mono 3.10.0.
-k
If you have an example of the release that would be awesome, concrete examples definitely help with testing.
@Taloth do you have the same issue (or are you not running Sonarr on the same machine that has the ZFS volume(s))? The disk space check on non-Windows (running mono) is pretty simple and looks for local disks, which causes issues with ZFS volumes as well as some other JBOD configurations, in addition to network drives.
Markus:
medialib@lateralus:/cage/1/downloads/torrent-seed/NCIS S10 720p HDTV$ find . -name *.rar -exec unrar v {} ; | grep -i s010
Volume ./NCIS.S010E16.720p.HDTV.X264-DIMENSION/in.sea.eyes.1016.720p-dimension.rar
NCIS.S010E16.720p.HDTV.X264-DIMENSION.mkv
Note the mkv filename having “NCIS.S010E*”, it was isolated to one episode in the entire episode pack, so it was easy to find and rectify 
Taloth,
Sonarr is on the same machine. It’s a local volume, a single (but very large) disk pool mounted as zfs in mountpoint /cage/1. It’s roughly 19TB in size, about half used.
Yes, I see the same thing, but it never bothered me so I didn’t look into it when I first noticed.
Tbh I kinda pushed it ahead coz I want to implement a method to identify volumes so we can safely determine if a move crosses FS boundaries. Low prio.