You are here: Home » Reply

Reply To: Scanning outside of the specified directories?



@fizze wrote:

Ok, that looks reasonable.
Care to post your mount status? 😉
What fs types do you use?

Sure… I have two SATA HDDs. The Linux partitions are ext3.

mount output:

/dev/sda6 on / type ext3 (rw,relatime,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
/sys on /sys type sysfs (rw,noexec,nosuid,nodev)
varrun on /var/run type tmpfs (rw,noexec,nosuid,nodev,mode=0755)
varlock on /var/lock type tmpfs (rw,noexec,nosuid,nodev,mode=1777)
udev on /dev type tmpfs (rw,mode=0755)
devshm on /dev/shm type tmpfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
lrm on /lib/modules/2.6.24-24-generic/volatile type tmpfs (rw)
/dev/sda7 on /home type ext3 (rw,relatime)
/dev/sda8 on /media/sda8 type ext3 (rw,relatime)
/dev/sda9 on /media/sda9 type ext3 (rw,relatime)
/dev/sdb2 on /media/storage type ext3 (rw,relatime)

/dev/sdb1 on /media/winnew type fuseblk (rw,nosuid,nodev,allow_other,default_permissions,blksize=4096)
/dev/sda1 on /media/winold type fuseblk (rw,nosuid,nodev,allow_other,default_permissions,blksize=4096)
securityfs on /sys/kernel/security type securityfs (rw)
rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
nfsd on /proc/fs/nfsd type nfsd (rw)

The relevant parts (sda9, storage and home) are written in bold.

@fizze wrote:

I’ve never seen anything like this, and I’ve used firefly over multiple disks also.
Could it be there are hardlinks that cause firefly to trip?

I am not entirely sure I understand what you mean by hardlinks. Are you referring to the names of the devices – or to the devices themselves?

As for any symlinks pointing to the home partition, there’s none. (I even removed the only broken symbolic link pointing there.)

Next, I followed your suggestion. Maybe there is something wrong with mt-daapd and mp3_dir referring to locations on two different hard drivers.

So I replaced

mp3_dir = /media/storage,/media/sda9


mp3_dir = /media/storage

Re-ran the test… it all went fine. However, when I added the second location (/media/sda9), it began scanning /home/alex (and also crashed, same as before).

Then I started it only with

mp3_dir = /media/sda9

Same erratic behavior (scanning in home, crash).

The interesting bit is that, as you can see, both /media/sda9/ and /home are parts of the same physical hard drive.

It shouldn’t make any difference, but just to make sure:

fdisk -l

Disk /dev/sda: 400.0 GB, 400088457216 bytes
255 heads, 63 sectors/track, 48641 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x8f8004b0

Device Boot Start End Blocks Id System
/dev/sda1 * 1 7833 62918541 7 HPFS/NTFS
/dev/sda2 7834 48641 327790260 5 Extended
/dev/sda5 7834 8029 1574338+ 82 Linux swap / Solaris
/dev/sda6 8030 10640 20972826 83 Linux
/dev/sda7 10641 13251 20972826 83 Linux
/dev/sda8 13252 15862 20972826 83 Linux
/dev/sda9 15863 48641 263297286 83 Linux

Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000c54f2

Device Boot Start End Blocks Id System
/dev/sdb1 * 1 15680 125949568+ 7 HPFS/NTFS
/dev/sdb2 15681 60801 362434432+ 83 Linux

I also have enough free space on all devices:

 df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda6 20G 3.4G 16G 18% /
varrun 1014M 300K 1014M 1% /var/run
varlock 1014M 0 1014M 0% /var/lock
udev 1014M 72K 1014M 1% /dev
devshm 1014M 0 1014M 0% /dev/shm
lrm 1014M 40M 975M 4% /lib/modules/2.6.24-24-generic/volatile
/dev/sda7 20G 13G 6.3G 67% /home
/dev/sda8 20G 19G 312M 99% /media/sda8
/dev/sda9 248G 218G 18G 93% /media/sda9
/dev/sdb2 341G 281G 43G 87% /media/storage
/dev/sdb1 121G 46G 75G 39% /media/winnew
/dev/sda1 61G 15G 46G 25% /media/winold

There are just 56 symbolic links on the whole sda9 partition… most are broken, pointing to where-some-mount-points-used-to-be. If you think it’s relevant, I’ll post that. Although… there’s nothing even mentioning “home” there. :-/

Well, at least we’re narrowing the field. There’s obviously something wrong in some cases when the media directories are on different physical hard drives.