Sabnzbd/CP/SB moved items not moving off of landing zone

[dekthro]

After I had innitially set this all up everything was working quite well. I added in a new hard drive, added it to the HDA per the wiki guide (as I did with previous drives), and added it into the Greyhole pool. I am not sure if this is related or not, but this is when I noticed files were just pooling up in my /lz instead of actually being spread over the drives (as previously this has been happening without issue).

Now it is as if Greyhole does not even see files after they have finished downloading, and Sickbeard/CP move them to their respective shares.

Code: Select all

3.13.5-101.fc19.x86_64 samba-4.0.13-1.fc19.x86_64 amahi-greyhole-0.9.44-2.x86_64

Code: Select all

Disk /dev/sda: 1000.2 GB, 1000203804160 bytes, 1953523055 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk label type: dos Disk identifier: 0x00051593 Device Boot Start End Blocks Id System /dev/sda1 63 1953523054 976761496 83 Linux Disk /dev/sdb: 1000.2 GB, 1000203804160 bytes, 1953523055 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk label type: dos Disk identifier: 0x0007a9b7 Device Boot Start End Blocks Id System /dev/sdb1 63 1953523054 976761496 83 Linux Disk /dev/sdc: 2000.4 GB, 2000398934016 bytes, 3907029168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk label type: dos Disk identifier: 0x00076930 Device Boot Start End Blocks Id System /dev/sdc1 2048 3907028991 1953513472 83 Linux Disk /dev/sdd: 200.0 GB, 200048565760 bytes, 390719855 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk label type: dos Disk identifier: 0x0009716d Device Boot Start End Blocks Id System /dev/sdd1 * 2048 411647 204800 83 Linux /dev/sdd2 411648 20891647 10240000 83 Linux /dev/sdd3 20891648 41371647 10240000 83 Linux /dev/sdd4 41371648 390719854 174674103+ 5 Extended /dev/sdd5 41373696 53661695 6144000 82 Linux swap / Solaris /dev/sdd6 53663744 382552063 164444160 83 Linux /dev/sdd7 382554112 390713343 4079616 83 Linux [root@localhost log]# df -h Filesystem Size Used Avail Use% Mounted on /dev/sdd2 9.5G 2.9G 6.2G 32% / devtmpfs 2.0G 0 2.0G 0% /dev tmpfs 2.0G 0 2.0G 0% /dev/shm tmpfs 2.0G 540K 2.0G 1% /run tmpfs 2.0G 0 2.0G 0% /sys/fs/cgroup tmpfs 2.0G 56K 2.0G 1% /tmp /dev/sda1 917G 72G 799G 9% /var/hda/files/drives/drive1 /dev/sdb1 917G 28G 843G 4% /var/hda/files/drives/drive2 /dev/sdc1 1.8T 98G 1.7T 6% /var/hda/files/drives/drive4 /dev/sdd1 190M 76M 101M 44% /boot /dev/sdd3 9.5G 23M 9.0G 1% /home /dev/sdd6 155G 142G 5.2G 97% /lz

None of the mysql commands worked.

Code: Select all

Greyhole Work Queue Statistics ============================== This table gives you the number of pending operations queued for the Greyhole daemon, per share. Write Delete Rename Check Books 0 0 0 0 Docs 0 0 0 0 Movies 0 0 0 0 Music 0 0 0 0 Pictures 0 0 0 0 Public 0 0 0 0 TV 0 0 0 0 Videos 0 0 0 0 ============================================ Total 0 0 0 0 Write Delete Rename Check The following is the number of pending operations that the Greyhole daemon still needs to parse. Until it does, the nature of those operations is unknown. Spooled operations that have been parsed will be listed above and disappear from the count below. Spooled 0

None of the Mysql commands from the troubleshooting page were working. But drive1, drive2 an drive4 are in the storage pool currently.

[bigfoot65]

Did you check to see if the gh folder exists on the new drive? If not, you can manually create it. Also did you do greyhole -f after adding the drive?

Recommend you check the /var/log/greyhole.log for errors as well.

[dekthro]

Sorry for the delay. Yeah running greyhole -f does move everything off the landingzone, the problem is that it seems to be that that is the only way for it to happen.

[bigfoot65]

Do you have mount shares locally installed?
https://wiki.amahi.org/index.php/Mount_Shares_Locally

Any time you mess with files locally with Greyhole, need to use this script. You also reference the /mnt/samba/share and not the /var/hda/files/share folder.

[dekthro]

Just to preface, I do have my landing zone in its own partition as /lz. I believe I did that all correctly and ran the script at the end of the guide, and it created /mnt/apache and /mnt/samba, though I'm not seeing any of the share data in there. Do I need to migrate this somehow?

[bigfoot65]

Post subject: Re: Sabnzbd/CP/SB moved items not moving off of landing zone Reply with quote
Do you have mount shares locally installed?
https://wiki.amahi.org/index.php/Mount_Shares_Locally

Did you install this script? You did not indicate it in your post that you did. You would see shares in /mnt/samba if you did. There is no /mnt/apache that I am aware unless that is something you did.

[dekthro]

Sorry for not being clear. I did follow that guide and run the script. At the end of the Wiki page there is also "Updated script for Greyhole users" which addresses Sickbeard usage, which is where the /mnt/apache came from.

/mnt/samba does indeed exist, and I do see the shares reflected in there. Though, not the contents of my greyhole pool.

[bigfoot65]

The script at the end may not work. It is not an official Amahi greyhole script. A user contributed that, so we have not tested.

If you are not seeing what is in the Greyhole storage pool, you may need to run greyhole -f.

I would be cautious using an unsupported script.

[dekthro]

Noted. I have run greyhole -f but /mnt/samba/ still is not reflecting what is in the shares.

Though now that I think about it, this is probably my error whilst going through the Mount_Shares_Locally script.

What should username be set to through out? root? I had set it to my personal username, which I feel like now is incorrect.

[bigfoot65]

The script states to make it your 1st admin user, not root. If you make files root owned, most apps will not be able to access them.

The modified script you are using is incorrect. You need to replace:

testparm -s /etc/samba/smb.conf 2>/dev/null | grep "^\[" | grep -v "\[global\]" | grep -v "\[homes\]" | awk -F'[' '{print $2}' | awk -F']' '{print $1}' | xargs -d "\n" mkdir -p

with

mysql -u root -phda -e "select comment from shares" hda_production | grep -v "^comment$" | xargs -d "\n" mkdir -p

I will update the wiki accordingly. This may be why you are having issues.