Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Old drives still referenced #206

genelatham opened this issue Apr 20, 2019 · 2 comments


None yet
2 participants
Copy link

commented Apr 20, 2019

NOTE ALSO: I use greyhole on an Amahi server. References to "wiki" are Amahi wiki.

NOTE: i collected all of the information requested in the Wiki article. Even with much of the info going to apaste the result was quite lengthy so I apasted it as well, the information can be found at: ... UwkUJa96wQ

Some background:
I am upgrading and cleaning up my system which has been running since late 2012 (it's be through several upgrades). When I upgraded from Amahi 7 to Amahi 11 I did it by creating a new HDA and moving the disks over. This worked well enough, but there were some problems in resetting the shares (my fault) and it resulted in some duplicate information on disk. Since I had been wanting to rename the mount points for the pool disks, I thought I would take the drives off line one at a time, clean them up and put them back on line with the new names I wanted. Before I started I added some scratch disks to the pool to be sure there would be plenty of room. (These disks are mounted at /var/hda/drives/pool5 and /var/hda/drives/pool6.)

I started with the oldest disk (which is named WD-2). I did a "greyhole --going" on the drive. (I also unchecked it in the Drive Pooling->Partitions tab.) It took about 20 hours to move everything off of the drive and do the fsck. After the fsck for the "going" finished I did an additional one: "greyhole --fsck -o -m", just to insure nothing got lost.

I cleared off WD-2 and added it back as /var/hda/drives/pool2. I followed this with a "greyhole --fsck -o -m". Everything seems fine and as near as I can tell nothing got lost.

The problem:
Now whenever an fsck is run I get tens of thousands of messages like this (with different file names, of course):

Apr 18 15:00:03 WARN fsck: Found a metadata file pointing to a drive not defined in your storage pool: '/var/hda/drives/wd-2/gh/Backups/Photos/'. Will mark it as Gone.

I have run the fsck several times, the errors remain and don't appear to be fixed. Is there any way to clean this up? It makes it hard to dig through the log to see if fsck found anything real.



This comment has been minimized.

Copy link

commented Apr 21, 2019

It indeed looks like this warning is logged even if the metadata file is already marked as Gone. I implemented a fix here: 3399724
I created a new version 0.10.20 that includes this fix.

After upgrading, you can test by running a fsck on only a small directory that generated those errors:

greyhole --fsck --email-report --dir="/var/hda/files/ShareName/path/to/folder"

@gboudreau gboudreau closed this Apr 21, 2019


This comment has been minimized.

Copy link

commented Apr 22, 2019

I have tested this and does indeed seem to fix the problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.