[SOLVED] Greyhole Won't Start??

[jbmia]

Hi guys.. following is my troubleshooting information. Not sure if it's related, but I had an issue with my system partition filling up that I've since addressed. This has happened a couple times in the past and it's resulted in a corrupted mysql databases for zoneminder, so I checked their first with the greyhole db. I ran database repairs on the 3 greyhole tables, all seemingly repaired okay. I also captured the following from boot.log.1:

Code: Select all

Starting monit: /etc/monit.d/greyhole.conf:3: Warning: the executable does not exist '/etc/init.d/greyhole' /etc/monit.d/greyhole.conf:4: Warning: the executable does not exist '/etc/init.d/greyhole' ^[[60G[^[[0;32m OK ^[[0;39m]

In addition you'll note below that greyhole is showing as installed twice... (2 subsequent release updates) ??? Not sure if this is all related to the issue I had with my system partition, but my first thought is that a greyhole update was in the midst of being performed somewhere around the time the system partition filled up. I have no other explanation for the missing "/etc/init.d/greyhole" file.

Any guidance would be immensely appreciated!!

1. What version of Fedora, Samba & Greyhole are you running?

Code: Select all

[root@9745 /]# uname -r 2.6.35.14-106.fc14.x86_64 [root@9745 /]# rpm -q samba hda-greyhole samba-3.5.11-79.fc14.x86_64 hda-greyhole-0.9.26-2.x86_64 hda-greyhole-0.9.26-3.x86_64

2. The content of the /etc/samba/smb.conf & /etc/greyhole.conf files (provide paste URLs):
http://fpaste.org/zKxy/
http://fpaste.org/61sj/

3. The result of the following commands:

mount:

Code: Select all

/dev/mapper/vg_9745-lv_root on / type ext4 (rw) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) tmpfs on /dev/shm type tmpfs (rw) /dev/sdg1 on /boot type ext4 (rw) /dev/mapper/vg_9745-lv_home on /home type ext4 (rw) /dev/sdg3 on /var/hda/files type ext4 (rw) /dev/sdc1 on /var/hda/files/drives/drive1 type ext4 (rw) /dev/sdd1 on /var/hda/files/drives/drive2 type ext4 (rw) /dev/sdh1 on /var/hda/files/drives/drive3 type ext4 (rw) /dev/sdi1 on /var/hda/files/drives/drive4 type ext4 (rw) /dev/sdf1 on /var/hda/files/drives/drive6 type ext4 (rw) /dev/sdj1 on /var/hda/files/drives/drive9 type ext4 (rw) /dev/sda1 on /var/hda/files/drives/drive12 type ext4 (rw) /dev/sda2 on /var/media type ext4 (rw) /dev/sde1 on /zmd type ext3 (rw) /zmd/zm/images on /var/www/zm/images type none (rw,bind) /zmd/zm/events on /var/www/zm/events type none (rw,bind) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw) //127.0.0.1/Fanart on /mnt/samba/Fanart type cifs (rw)

fdisk -l

Code: Select all

Disk /dev/sda: 2000.4 GB, 2000398934016 bytes 255 heads, 63 sectors/track, 243201 cylinders, total 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 identifier: 0x000b7363 Device Boot Start End Blocks Id System /dev/sda1 2048 2867202047 1433600000 83 Linux /dev/sda2 2867202048 3907028991 519913472 83 Linux Disk /dev/sdb: 250.1 GB, 250059350016 bytes 255 heads, 63 sectors/track, 30401 cylinders, total 488397168 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 identifier: 0xd16ce398 Device Boot Start End Blocks Id System /dev/sdb1 2048 488396799 244197376 83 Linux Disk /dev/sdc: 1000.2 GB, 1000204886016 bytes 255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 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 identifier: 0xc87ee887 Device Boot Start End Blocks Id System /dev/sdc1 2048 1953523711 976760832 83 Linux Disk /dev/sdd: 1000.2 GB, 1000204886016 bytes 255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 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 identifier: 0x4bafc7b3 Device Boot Start End Blocks Id System /dev/sdd1 2048 1953523711 976760832 83 Linux Disk /dev/sde: 300.1 GB, 300090728448 bytes 243 heads, 63 sectors/track, 38285 cylinders, total 586114704 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 identifier: 0xd16ce393 Device Boot Start End Blocks Id System /dev/sde1 2048 586114703 293056328 83 Linux Disk /dev/sdf: 1000.2 GB, 1000204886016 bytes 255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 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 identifier: 0x5c2ff997 Device Boot Start End Blocks Id System /dev/sdf1 2048 1953523711 976760832 83 Linux Disk /dev/sdg: 500.1 GB, 500107862016 bytes 255 heads, 63 sectors/track, 60801 cylinders, total 976773168 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 identifier: 0x000b3c51 Device Boot Start End Blocks Id System /dev/sdg1 * 2048 1026047 512000 83 Linux /dev/sdg2 1026048 78850047 38912000 8e Linux LVM /dev/sdg3 78850048 771973119 346561536 83 Linux Disk /dev/sdh: 1500.3 GB, 1500301910016 bytes 255 heads, 63 sectors/track, 182401 cylinders, total 2930277168 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 identifier: 0x18249b79 Device Boot Start End Blocks Id System /dev/sdh1 2048 2930276351 1465137152 83 Linux Disk /dev/sdi: 2000.4 GB, 2000398934016 bytes 255 heads, 63 sectors/track, 243201 cylinders, total 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 identifier: 0x29cd4bd0 Device Boot Start End Blocks Id System /dev/sdi1 2048 3907028991 1953513472 83 Linux Disk /dev/sdj: 2000.4 GB, 2000398934016 bytes 255 heads, 63 sectors/track, 243201 cylinders, total 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 identifier: 0x000bc6a4 Device Boot Start End Blocks Id System /dev/sdj1 2048 3907028991 1953513472 83 Linux Disk /dev/dm-0: 4395 MB, 4395630592 bytes 255 heads, 63 sectors/track, 534 cylinders, total 8585216 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 identifier: 0x00000000 Disk /dev/dm-0 doesn't contain a valid partition table Disk /dev/dm-1: 30.0 GB, 30031216640 bytes 255 heads, 63 sectors/track, 3651 cylinders, total 58654720 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 identifier: 0x00000000 Disk /dev/dm-1 doesn't contain a valid partition table Disk /dev/dm-2: 5368 MB, 5368709120 bytes 255 heads, 63 sectors/track, 652 cylinders, total 10485760 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 identifier: 0x00000000 Disk /dev/dm-2 doesn't contain a valid partition table

df -h:

Code: Select all

Filesystem Size Used Avail Use% Mounted on /dev/mapper/vg_9745-lv_root 28G 23G 3.5G 87% / tmpfs 3.8G 4.0K 3.8G 1% /dev/shm /dev/sdg1 485M 67M 393M 15% /boot /dev/mapper/vg_9745-lv_home 4.9G 3.3G 1.4G 71% /home /dev/sdg3 326G 46G 264G 15% /var/hda/files /dev/sdc1 917G 826G 92G 90% /var/hda/files/drives/drive1 /dev/sdd1 917G 831G 87G 91% /var/hda/files/drives/drive2 /dev/sdh1 1.4T 1.3T 93G 94% /var/hda/files/drives/drive3 /dev/sdi1 1.8T 1.8T 91G 96% /var/hda/files/drives/drive4 /dev/sdf1 917G 825G 93G 90% /var/hda/files/drives/drive6 /dev/sdj1 1.8T 1.8T 93G 95% /var/hda/files/drives/drive9 /dev/sda1 1.4T 1.2T 93G 93% /var/hda/files/drives/drive12 /dev/sda2 489G 425G 39G 92% /var/media /dev/sde1 276G 212G 50G 82% /zmd //127.0.0.1/Fanart 489G 450G 39G 93% /mnt/samba/Fanart

greyhole --stats​: (note that I had 2gb in "trash" that emptied that isn't reflected above)

Code: Select all

Greyhole Statistics =================== Storage Pool Total - Used = Free + Trash = Possible /var/hda/files/drives/drive1/gh: 917G - 677G = 240G + 0G = 240G /var/hda/files/drives/drive2/gh: 917G - 777G = 140G + 0G = 140G /var/hda/files/drives/drive3/gh: 1375G - 1042G = 333G + 0G = 333G /var/hda/files/drives/drive4/gh: 1834G - 1477G = 357G + 0G = 357G /var/hda/files/drives/drive6/gh: 917G - 743G = 174G + 0G = 174G /var/hda/files/drives/drive9/gh: 1834G - 1215G = 619G + 0G = 619G /var/hda/files/drives/drive12/gh: 1346G - 474G = 803G + 0G = 803G ========================================== Total: 9139G - 6405G = 2666G + 0G = 2666G

4. The list drives in your storage pool (per Amahi platform):

Code: Select all

+----+-------------------------------+--------------+---------------------+---------------------+ | id | path | minimum_free | created_at | updated_at | +----+-------------------------------+--------------+---------------------+---------------------+ | 2 | /var/hda/files/drives/drive1 | 10 | 2011-04-08 17:48:11 | 2011-04-08 17:48:11 | | 3 | /var/hda/files/drives/drive2 | 10 | 2011-04-08 17:48:12 | 2011-04-08 17:48:12 | | 4 | /var/hda/files/drives/drive3 | 10 | 2011-04-08 17:48:12 | 2011-04-08 17:48:12 | | 5 | /var/hda/files/drives/drive4 | 10 | 2011-04-08 17:48:13 | 2011-04-08 17:48:13 | | 7 | /var/hda/files/drives/drive6 | 10 | 2011-04-08 17:48:15 | 2011-04-08 17:48:15 | | 8 | /var/hda/files/drives/drive9 | 10 | 2011-07-06 01:50:26 | 2011-07-06 01:50:26 | | 9 | /var/hda/files/drives/drive12 | 10 | 2012-03-15 22:43:19 | 2012-03-15 22:43:19 | +----+-------------------------------+--------------+---------------------+---------------------+

5. A list of the directories on the root of the drives included in your storage pool, obtained with the following command (provide a paste URL):
http://fpaste.org/zRUR/

6. The Greyhole work queue:

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 Home_Movies 0 0 0 0 Media_Remote 0 0 0 0 Movies 0 0 0 0 Music 0 0 0 0 Pictures 0 0 0 0 Public 0 0 0 0 Recipes 0 0 0 0 Software 0 0 0 0 TV 0 0 0 0 Users 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

[bigfoot65]

See this thread. Similar problem.

viewtopic.php?f=39&t=4494

[jbmia]

Hmmm... I'd checked the thread and deleted the greyhole repo, but oddly when I went back to remove hda-greyhole-0.9.26-3.x86_64, it couldn't be found... I then ran the "uname -r; rpm -q samba hda-greyhole" command and got:

Code: Select all

2.6.35.14-106.fc14.x86_64 samba-3.5.11-79.fc14.x86_64 hda-greyhole-0.9.26-4.x86_64

So, all I did was delete the greyhole.repo file, but it appears the issue was already resolved between the time I posted my initial request and now. It looks like a "0.9.26-4" release must have came out today sometime and auto updated... Not sure how the original "-2" and "-3" versions were removed. I verified greyhole is running...


Couple questions for any one who might have answers:
- any idea how this issue resolved itself?
- whose greyhole version is this "-4" version I now have installed? The Amahi version or the Repo version? If the latter, perhaps I should add the Repo back.

jbmia

[bigfoot65]

The reason it resolved itself is exactly as you stated, version 0.9.26-4. With the repo enabled, you will always get the latest version. With that comes risk that it may break something.

My advice would be to leave the autoupdate for the repo disabled. You can manually do an update when a new version comes out. I do not use the repo for just that reason. When a new version is installed, typically the older one is removed automatically.

So in short, it did resolve itself.

[jbmia]

Thank you for clarifying sir.!