Amahi Forums

I used the --going option on the second partition of my system drive. I want to remove this 210GB partition from the pool and use it solely as my landing zone.

I let --going run and completely (said it was successful) and according to the amount of used space on the other drives, everything looks okay. However, the original partition that I ran --going on still has all of the data there. Is this normal?

My assumption was that files would be copied over and then removed from the original location, but instead they're just copied and left in both places? Is this correct?

Hi Andy, this is ok, the files on the drive to be removed are not deleted.

/jayrock

Okay, cool. That makes sense too.

So what I did after using --going was remove the partition from the pool and moved my landing zones there. However, most of this drive is still full. What can I safely delete? There seems to still be a lot of data taking up space under /var/hda/files/drives/drive1/share_name/. I thought these would just be pointers, but there's roughly 180GB of space being used.

Should I just move my landing zones back off of this partition, format it again, and then move them back on it again?

Wait for that to complete (see /var/log/greyhole.log).

Then: If you see the attic using a lot of space, you can empty it if you'd like:

I tried doing that, but since the drive isn't in the pool anymore, I don't think Greyhole touched it.

It also seems as though the files taking up space are not in /var/hda/files/drives/drive1/.gh, but are instead in /var/hda/files/drives/drive1/share_name/ (what is currently set as my landing zone).

--fsck will look in the landing zone, and move all files it finds in there into the storage pool directories (the gh folders).

So can I safely delete the data in /var/hda/files/drives/drive1/share_name/ after --fsck is finished?

If there are still files in there, it either means that share doesn't have the "Use Pool" checkbox checked, so it's not using Greyhole.
Of the Location of that share isn't /var/hda/files/drives/drive1/share_name (per /etc/samba/smb.conf, path = ... lines)

If you still have issues: http://forums.amahi.org/viewtopic.php?f=39&t=1989

The drive does NOT have "uses pool" checked. I don't want it in the pool. I really just want it there as my landing zone, I do not want it as part of the actual pool. I can post all the info asked for, but I'm not sure that it's relevant to the question I'm asking.

The drive in question was formerly part of the pool, I used --going on it and then removed it from the pool when --going finished. Then I set it as my landing zone for each share. Every share is set to use the pool.

My understanding was that I could use this drive as the landing zone and then Greyhole would move the files dropped into the landing zone into the pool. Is that not a correct assumption? Do my landing zones have to be a location on a drive within the pool?

In practice, my assumption seems to be true as the space used (on the drive in question) stays constant after all transfers finish and Greyhole finishes its thing. Everything seems to work properly. However, I still have data in the landing zone folders (var/hda/files/drives/drive1/share_name). Are these just the pointers?

What I'm trying to get at is that I have 180GB of data on a drive that is NOW just used for a landing zone and is not a part of the pool. Is this normal? If not, I'll post all the info needed.

No, it's not normal, unless you have a LOT of files.

Use 'du' to find what is using the space:
Then enter the directories that du says are too big, and repeat "du -sh *", and so on, until you find the files that take up this space.