Files Missing from Directories - Queue Steadily Growing

[gboudreau]

Code: Select all

greyhole --fsck --dir="/hda/files/Television/Nurse Jackie/Season 2/" greyhole --debug "nurse.jackie.s02e02.dvdrip.xvid-reward.sample.avi"

[mattrountree]

Code: Select all

greyhole --fsck --dir="/var/hda/files/Television/Nurse Jackie/Season 2/" fsck of /var/hda/files/Television/Nurse Jackie/Season 2/ has been scheduled. It will start after all currently pending tasks have been completed.

Code: Select all

greyhole -S Last logged action: sleep on 2011-04-13 12:30:20 (5s ago) Details: Only locked files operations pending... Sleeping.

Code: Select all

greyhole --debug "nurse.jackie.s02e02.dvdrip.xvid-reward.sample.avi" Debugging file operations for file named "/nurse.jackie.s02e02.dvdrip.xvid-reward.sample.avi" From DB ======= From logs ========= From filesystem =============== Landing Zone: ls: cannot access /nurse.jackie.s02e02.dvdrip.xvid-reward.sample.avi: No such file or directory Graveyard: File copies:

[gboudreau]

Check your /var/log/greyhole.log to find where the fsck you initiated took place.
Paste-bin all the lines about fsck:

Code: Select all

grep -i fsck /var/log/greyhole.log | fpaste

[mattrountree]

Code: Select all

http://fpaste.org/Z1dX/

[gboudreau]

Apr 13 11:58:41 7 fsck: More than 90000 tasks queued... Won't queue any more at this time.

greyhole --view-queue
[...]
Total 32 + 0 + 0 = 32

That seems contradictory... greyhole.log says there are more than 90k tasks queued... Why would --view-queue say differently..?

Maybe try to restart the Greyhole service. See if the greyhole.log still says there are more than 90k tasks queued.

Code: Select all

service greyhole restart tail -f /var/log/greyhole.log

Some more info to gather:

Code: Select all

ps auxww | grep -i greyhole greyhole --view-queue mysql -u greyhole -pgreyhole -e "select count(*) from tasks" greyhole tail -f /var/log/greyhole.log | head -100 | fpaste

[mattrountree]

I restarted the service and I still see the "More than 90000 tasks queued..." in the log

Code: Select all

ps auxww | grep -i greyhole root 29766 0.1 0.3 296600 12780 pts/1 SN 13:08 0:00 /usr/bin/php /usr/bin/greyhole --daemon root 29801 0.0 0.0 102760 828 pts/1 S+ 13:10 0:00 grep -i greyhole

Code: Select all

greyhole --view-queue Greyhole Work Queue Statistics ============================== This table gives you the number of pending operations queued for the Greyhole daemon, per share. Write Delete Rename Books 0 0 0 Completed 0 0 0 Docs 32 0 0 Movies 0 0 0 Music 0 0 0 Pictures 0 0 0 SendToLaptop 0 0 0 SendToPhone 0 0 0 SendToTran 0 0 0 Television 0 0 0 Torrentflux-b4rt 0 0 0 ================ Total 32 + 0 + 0 = 32 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 421

Code: Select all

mysql -u greyhole -pgreyhole -e "select count(*) from tasks" greyhole +----------+ | count(*) | +----------+ | 15713219 | +----------+

Code: Select all

http://fpaste.org/1q31/

From the log is it still processing the fsck?

[gboudreau]

Indeed... Those tons of tasks it's working on are the missing symlinks.
Those are indeed not listed by --view-queue (they probably should).
--fsck checks to find any broken file, and then, for each it finds, it creates a fsck_file task to be processed once all other tasks are completed.
So it's working on restoring your symlinks now.
I'd guess this would come from you moving the shares Locations or something of that sort.

Anyway, tail -f greyhole.log, or use greyhole -S, to see when it's done.

[mattrountree]

Thanks! OK, I'll just keep an eye on it and hopefully everything will work out. It doesn't look like I can run fsck on a specific dir until the "invisible" queue drops below 90K then?

[gboudreau]

Yes, you can, but the actual 'fixing' will be postponed until the end of the queue, so you won't see any concrete result of that last fsck until Greyhole reach that point.
But I'd say it started to fix everything, so just let it run, and your files should all be back once it's done.
You can always schedule another --fsck now, just to be sure:

Code: Select all

greyhole --fsck

[mattrountree]

No problem, I'm sure it will track them all down. Just wondering if I could prioritize certain directories somehow. It doesn't sound like it until the first fsck is done.

Thanks again. I'm headed to the donation page next