SOLVED: Greyhole Write Issues - WARN write: No metadata files could be created.

[johnny5shared]

I'm suffering (emotionally and electronically) from the same symptoms as this person: viewtopic.php?f=39&t=5592&p=37076#p37076

I wanted to create my own post since that one's marked as solved (their solution was no good for me).

During troubleshooting for the issue above (where Greyhole furiously spewed out failure to write logs), I checked my fstab and found two entries for the same drive. I set my drives up using the Amahi disk wizard app, one of the adds failed if I remember correctly so I tried again. I've had a lot of problems getting this going and this is my third clean install. I don't have it in me to try again.

I am accessing the HDA via SSH, and I took a copy of my fstab before deleting the first of the duplicate rows below. It was perhaps a bit wreckless, but after hours of troubleshooting Greyhole with the official page I figured I had nothing to loose.

Code: Select all

# # /etc/fstab # Created by anaconda on Sat Apr 30 20:32:50 2016 # # Accessible filesystems, by reference, are maintained under '/dev/disk' # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info # UUID=74c494ed-eaa9-4534-a5ef-85b093ece3c6 / xfs defaults 0 0 UUID=92b57522-6f5f-4583-aaa5-2f33afe8e8bd /boot ext4 defaults 1 2 UUID=f2ef8eab-b6fc-4983-879a-926312c9e110 swap swap defaults 0 0 UUID=3731b156-9ca4-4f4d-9675-c0663a31e9e9 /var/hda/files/drives/500blue auto auto,rw,exec 0 0 UUID=5442b602-a968-4d1a-a3fe-75af01a5716f /var/hda/files/drives/500blue auto auto,rw,exec 0 0 UUID=f1191347-1f18-4cf6-84a1-85fcc17343c6 /var/hda/files/drives/500green auto auto,rw,exec 0 0

Now the HDA won't start. Or rather, my monitor-less PC turns on and SSH doesn't come online. I'll have a monitor in a couple of days.

So firstly, can I restore my fstab file to get the HDA back up to troubleshoot my Greyhole issue? I assume I have to do it through Fedora somehow.

Secondly, was I right in deleting the duplicate entry? Should I have picked the other one?

Then. And I'll keep it here, because this is my main problem, I'll get the debug info and hopefully we can look at the Greyhole issue.

Thanks in advance:)

[johnny5shared]

OK I got the system back up by editing fstab on another linux machine (I couldn't boot to rescue since Amahi setup asks for no root).

Commenting out the second of the duplicate fstab works. So that's that put to bed. I'm now in the state I was before. I can copy files to my user folder on the HDA, no problem. But as soon as I copy to a share in the pool, I get a client OS error saying there's not enough space (it's a clean install with newly formatted drives). In the Greyhole log there are constant metadata write errors.

So Greyhole appears to be working. But it's struggling to complete the queue, or report drive capacity to the client OS properly.

[johnny5shared]

Code: Select all

$ uname -r; rpm -q samba amahi-greyhole 4.2.3-300.fc23.x86_64 samba-4.3.8-0.fc23.x86_64 amahi-greyhole-0.9.67-1.x86_64

Code: Select all

$ fpaste /etc/samba/smb.conf http://paste.fedoraproject.org/385768/10299514/ -> http://paste.fedoraproject.org/385768/10299514

Code: Select all

$ fpaste /etc/greyhole.conf Uploading (13.0KiB)... http://paste.fedoraproject.org/385770/3028146/ -> http://paste.fedoraproject.org/385770/03028146

Code: Select all

$ mount sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) devtmpfs on /dev type devtmpfs (rw,nosuid,size=1528792k,nr_inodes=382198,mode=755) securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755) tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755) cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd) pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime) cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset) cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer) cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb) cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio) cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event) cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio) cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices) cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory) configfs on /sys/kernel/config type configfs (rw,relatime) /dev/sda3 on / type xfs (rw,relatime,attr2,inode64,noquota) hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime) systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=31,pgrp=1,timeout=0,minproto=5,maxproto=5,direct) tmpfs on /tmp type tmpfs (rw) mqueue on /dev/mqueue type mqueue (rw,relatime) debugfs on /sys/kernel/debug type debugfs (rw,relatime) /dev/sdc1 on /var/hda/files/drives/500green type ext4 (rw,relatime,data=ordered) /dev/sdb1 on /var/hda/files/drives/500blue type ext4 (rw,relatime,data=ordered) /dev/sda1 on /boot type ext4 (rw,relatime,data=ordered) none on /var/spool/greyhole/mem type tmpfs (rw,relatime,size=4096k) tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=307340k,mode=700,uid=1000,gid=100) $ fdisk -l fdisk: cannot open /dev/sr0: Permission denied fdisk: cannot open /dev/sda: Permission denied fdisk: cannot open /dev/sdc: Permission denied fdisk: cannot open /dev/sdb: Permission denied $ df -h Filesystem Size Used Avail Use% Mounted on devtmpfs 1.5G 0 1.5G 0% /dev tmpfs 1.5G 0 1.5G 0% /dev/shm tmpfs 1.5G 484K 1.5G 1% /run tmpfs 1.5G 0 1.5G 0% /sys/fs/cgroup /dev/sda3 50G 2.1G 48G 5% / tmpfs 1.5G 32K 1.5G 1% /tmp /dev/sdc1 459G 70M 435G 1% /var/hda/files/drives/500green /dev/sdb1 459G 70M 435G 1% /var/hda/files/drives/500blue /dev/sda1 477M 74M 374M 17% /boot none 4.0M 0 4.0M 0% /var/spool/greyhole/mem tmpfs 301M 0 301M 0% /run/user/1000 $ greyhole --stats

Code: Select all

$ sudo mysql -u root -phda -e "select * from disk_pool_partitions" hda_production ERROR 1146 (42S02) at line 1: Table 'hda_production.disk_pool_partitions' doesn't exist

Code: Select all

ERROR 1146 (42S02) at line 1: Table 'hda_production.disk_pool_partitions' doesn't exist Uploading (0.6KiB)... http://paste.fedoraproject.org/385772/67103189/ -> http://paste.fedoraproject.org/385772/67103189

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 Movies 0 0 0 0 Music 0 0 0 0 Pictures 0 0 0 0 TV 0 0 0 0 Videos 0 0 0 0 ============================================ Total 0 0 0 0 Write Delete Rename Check

[johnny5shared]

OK so I tried this (adding /gh with mkdir to each of my shares) and the errors went away. I can't remember being told this in the instructions, but progress is progress . When I copy a file to a GH enabled share I don't get any more space errors (yay), and in the GH logs I see the file being distributed according to my rules.

Code: Select all

mysql -u root -phda -e "select * from disk_pool_partitions" hda_production

Still results in "ERROR 1146 (42S02) at line 1: Table 'hda_production.disk_pool_partitions' doesn't exist"

Any ideas... how can I be sure it's working correctly?

Note: navigating directly to the /gh dir on each of the drive indeed shows my test file on each. So other than the table error it looks like it's working.

Cheers!

[bigfoot65]

Will need some additional info.

Please post the /etc/greyhole.conf file contents along with the URL for:

Code: Select all

apaste --sysinfo

The manual work you are doing may cause more harm than good. None of the mkdir commands are necessary. Depending on the actual issue, you may have to start over with Greyhole.

We'll have to see based on the info requested.

[johnny5shared]

Thanks for the help...

/etc/greyhole.conf is above, my system info is as follows...

Code: Select all

$ http://paste.fedoraproject.org/386910/32766814/ -> http://paste.fedoraproject.org/386910/32766814

[bigfoot65]

Thanks for the info.

How did you install Greyhole? Follow any wiki guidance?

Also did you use the disk-wizard App or manually install the drives?

Most users have the greatest success with the manually adding a disk drive guidance and the greyhole-ui App.

What you have should work, but something is amiss based on the SQL errors. Might want to manually check that MariaDB is running:

Code: Select all

systemctl status mariadb

Also verify that there are tables in the Greyhole database. Try this SQL syntax:

Code: Select all

echo "select * from disk_pool_partitions" | mysql -u root -phda hda_production

[johnny5shared]

OK answers below:

How did you install Greyhole? Follow any wiki guidance?

I followed this

Also did you use the disk-wizard App or manually install the drives?

I used the disk wizard app (see my first post for some commentary about how I had, and eventually fixed a fstab error)

Most users have the greatest success with the manually adding a disk drive guidance and the greyhole-ui App.

What you have should work, but something is amiss based on the SQL errors. Might want to manually check that MariaDB is running:

Code: Select all

systemctl status mariadb

Maria DB is running

Also verify that there are tables in the Greyhole database.

Code: Select all

MariaDB [greyhole]> show tables -> ; +--------------------+ | Tables_in_greyhole | +--------------------+ | du_stats | | settings | | tasks | | tasks_completed | +--------------------+

[bigfoot65]

I don't see anything wrong looking at all the logs and files you have provided.

The only thing I can think of is it has something to do with the disk-wizard App.

I had problems with it, so did all my manually. I don't believe the SQL I provided will be in the Greyhole database as you set up Greyhole manually. If I remember correctly, that table is only created when using the greyhole-ui App.

The arguments in your /etc/fstab differ slightly from what the manual install guidance shows. Try unmounting the drives and changing auto auto,rw,exec 0 0 to defaults 1 2. Then remount them and restart Greyhole. See if that makes a difference.

[johnny5shared]

I can't seem to log in to MySQL root. Could that be an issue? Should I set up a root user? I 'll look at the fstab file again tonight.