I did all that and it shows up everywhere in the system as full capacity EXCEPT when I do greyhole -s and the two identical drives report different total sizes but show 627 gig free each with a difference in used size of about 50 gig. It's weird but it doesn't seem to be affecting anything.

Hi, I have a 1tb disk I'm trying to add and like the title says, gparted says "The driver descriptor says the physical block size is 2048 bytes, but Linux says it is 512 bytes." but it formats it at full capacity. When I add it to Greyhole and run greyhole -s from the shell it shows: Stora...

Ok it looks like I was unnecessarily complicating things. So it's install server, leave everything ALONE, format a drive, mount it, enable storage pool, watch magic happen. The log shows the files being moved to the drives in a round-robin fashion which I guess is sort of "RAID-0 meets JBOD&quo...

Ok so I should move /var/hda/files back to the boot drive... Somehow I figured I had to move the share volume off the first drive and on to the second. Can I do this in fstab without copying off everything? I changed the share path in the amahi control panel. Can I move the files in the shares manua...

What is the best place to find an overview of how greyhole does its thing? I don't want a white paper on it, just an executive overview if you will. It seems like you copy a bunch of stuff and it fills up the first drive and either you copied less than the max capacity and it sorts it out overnight ...

Ok well now I'm still having an issue. Got a disk full error from drive 2 after copying to the smb share from another drive. Drives 2 and 3 are in the greyhole.conf and both are visible in the Storage Pool page and are selected. Edit: Nevermind, I guess.... did a sudo greyhole -fo and now the log is...

As it turns out, it wasn't a permissions problem - it was a bunch of symlinks that weren't visible on the client but I saw on the server. I moved the data out of the gh directory and merged it back into the share directory. Nothing had left the 2nd drive yet but I guess greyhole was doing something ...

Yeah, it's unrelated. Plus I apparently have a permissions issue - files are there on the server but hidden from my user. That's no big deal though.

Well thank you very much! That fixed it for me, now I just have to edit samba.config to fix the inability to browse shares from the server itself.

I added both drives (2 and 3) to the pool and now greyhole -s shows the service doing something.

Ok so if I understand I leave /var/hda/files on drive 1 and point the shares manually to drive 2 in the control panel, then add drives 2 and 3 to the pool?

[ Post made via Android ]