Greyhole messed up (again) need help
Posted: Thu Dec 13, 2012 5:38 pm
So, today I noticed that a few dozen files went missing since last night in my movies folder. I dug around the /gh/ directories and, thankfully found the files. What seems to have happened is that I changed a few folder names on the Movies share (it was the share and not the actual directory on the server) and Greyhole didn't keep up with it.
The nature of the changes were like this: /movies/Show/Show Season 1/ to /movies/Show/Season 1/
In the /gh/ directories the subfolders are still named /Show Season 1/.
So I ran greyhole -f and that didn't help. Then I ran greyhole --debug /var/hda/files/movies/Show it listed a bunch or 'write pending task' for files in the one subdirectory I didn't change, and hadn't lost any files, followed by this gem:
So what do I do now?
P.S. One other nagging issue. Whenever I issue a command to Greyhole, it spits this out:
P.P.S. I also just noticed that in the "Servers" section of the Dashboard it shows that Grayhole Server as being off, even though it does respond to commands. I tried giving it a service greyhole restart and it responded with this.
So, apparently it's trying to allocate 4.3 gigabytes of memory?
Here's what the log has to say when I try and start the grehole service.
It's at that last log entry that greyhole take a dump. Oddly, the file it's trying to fsck (the name I've changed to protect the innocent ) isn't supposed to be in the music directory, it's a movie file located in the /Movies share. I don't know why it's listed as being there - perhaps corruption of the greyhole DB?
I've looked in the graveyard directory where it's getting stuck and cannot find tombstone for the mkv file it's looking for.
I have made a little progress. In an effort to rebuild the /Movies share I fist backed up the contents of the landing zone (entirely symlinks) and then blew them all out with
I then scheduled a fsck task on the /Music directory, telling it not to walk the graveyard, since that's where the problem is occurring, so maybe it can get past the issue.
Then manually launched the daemon
It seems to be working! Hopefully it'll rebuild the /Movies share. However, I have concerns about the root issue of the /Music tombstone it's looking for, and getting stuck on.
Failure. So greyhole worked for a few minutes fsck-ing when it took a dump at the same spot it always does,
Last Log Entry
Terminal Return
The nature of the changes were like this: /movies/Show/Show Season 1/ to /movies/Show/Season 1/
In the /gh/ directories the subfolders are still named /Show Season 1/.
So I ran greyhole -f and that didn't help. Then I ran greyhole --debug /var/hda/files/movies/Show it listed a bunch or 'write pending task' for files in the one subdirectory I didn't change, and hadn't lost any files, followed by this gem:
Code: Select all
From filesystem
===============
Landing Zone:
ls: cannot access /hda/files/movies/Show: No such file or directory
P.S. One other nagging issue. Whenever I issue a command to Greyhole, it spits this out:
Code: Select all
PHP Warning: date_default_timezone_get(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PST/-8.0/no DST' instead in /usr/bin/greyhole on line 39
P.P.S. I also just noticed that in the "Servers" section of the Dashboard it shows that Grayhole Server as being off, even though it does respond to commands. I tried giving it a service greyhole restart and it responded with this.
Code: Select all
PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 4686721024 bytes) in /usr/bin/greyhole on line 1916
Here's what the log has to say when I try and start the grehole service.
Code: Select all
Dec 15 07:46:34 7 daemon: Loading graveyard backup directories...
Dec 15 07:46:34 7 daemon: Found 2 directories in the settings table.
Dec 15 07:46:34 7 daemon: More than 900 tasks queued... Won't queue any more at this time.
Dec 15 07:46:34 7 simplify_tasks: Simplifying pending tasks.
Dec 15 07:46:35 7 simplify_tasks: More than 900 tasks queued... Won't queue any more at this time.
Dec 15 07:46:35 7 fsck_file: Now working on task ID 920813: fsck_file Music/Artist/album/file.mkv
Dec 15 07:46:35 7 fsck_file: Music/Artist/album/file.mkv...
I've looked in the graveyard directory where it's getting stuck and cannot find tombstone for the mkv file it's looking for.
Code: Select all
ls '/var/hda/files/gh/.gh_graveyard/Music/Artist/album/'
Code: Select all
rm -rf /var/hd/files/movies/*
Code: Select all
greyhole -fyd /var/hda/files/music
Code: Select all
greyhole -D
Failure. So greyhole worked for a few minutes fsck-ing when it took a dump at the same spot it always does,
Last Log Entry
Code: Select all
task ID 920813: fsck_file Music/Artist/album/file.mkv
Loading tombstones for Music/Artist/album/file.mkv...
Code: Select all
PHP Fatal error: Allowed memory size of 167772160 bytes exhausted (tried to allocate 4686721024 bytes) in /usr/bin/greyhole on line 1919