SOLVED: Root full, so I moved the landing zone. Root is still full.

johnny5shared
Posts: 29
Joined: Sat Apr 02, 2016 1:48 am

Re: Root full, so I moved the landing zone. Root is still full.

Postby johnny5shared » Thu Jul 07, 2016 7:15 pm

fstab

Code: Select all

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=f1191347-1f18-4cf6-84a1-85fcc17343c6 /var/hda/files/drives/500green auto auto,rw,exec 0 0 UUID=7db4c996-2e30-4b5c-9a2b-71d4b9ed4f39 /var/hda/files/drives/1tbDisk auto auto,rw,exec 0 0
No, root is not a part of GH (i.e. not referenced in the GH config)

Trying to unmount and run that du now. Will edit this comment when I have a result :)

johnny5shared
Posts: 29
Joined: Sat Apr 02, 2016 1:48 am

Re: Root full, so I moved the landing zone. Root is still full.

Postby johnny5shared » Thu Jul 07, 2016 7:43 pm

Ok, this could be interesting. With 1tbDisk unmounted (and the other GH disks) I get this...

Code: Select all

50623812 /var 49900276 /var/hda 49697072 /var/hda/files/drives/1tbDisk/gh 49697072 /var/hda/files/drives/1tbDisk 49697072 /var/hda/files/drives 49697072 /var/hda/files 49639048 /var/hda/files/drives/1tbDisk/gh/Pictures 32219448 /var/hda/files/drives/1tbDisk/gh/Pictures/320GB Spare 14392332 /var/hda/files/drives/1tbDisk/gh/Pictures/320GB Spare/Camera Uploads 14223928 /var/hda/files/drives/1tbDisk/gh/Pictures/Limux Photos
Is this because this drive is also my landing zone? - It's definitely unmounted. I ran "sudo umount /var/hda/files/drives/mydrive" for each of the non root drives (double checked)

User avatar
bigfoot65
Project Manager
Posts: 11241
Joined: Mon May 25, 2009 4:31 pm

Re: Root full, so I moved the landing zone. Root is still full.

Postby bigfoot65 » Fri Jul 08, 2016 5:17 am

Is this because this drive is also my landing zone?
If the LZ is on the drive you unmounted, it would not reflect in the stats now.

Try doing:

Code: Select all

df -h
Did you have the 1TB drive mounted when you moved the LZ and files initially? Verify if these files are located on the 1TB drive and in the directory with it unmounted. They may be duplicated, root drive and 1TB drive.

If you can confirm these files are located on the 1TB drive, you could remove the /var/hda/files/drives/1tbDisk directory. That should restore the space to your root drive. I would be cautious though if you don't have a backup.
ßîgƒσστ65
Applications Manager

johnny5shared
Posts: 29
Joined: Sat Apr 02, 2016 1:48 am

Re: Root full, so I moved the landing zone. Root is still full.

Postby johnny5shared » Sat Jul 09, 2016 12:35 am

Thanks for the help bigfoot. As it happens a friend suggested the same thing. You're dead on.

When adding the new drive I must have synced some files before it was properly mounted. That's confusing as hell. I didn't know you could mount a dir on a non empty dir. Many hours lost troubleshooting that one. Hopefully someone finds this and avoids the same rigmarole.

The upside is I'm well versed in Amahi, Greyhole and Linux basics now :)

Here are my steps should they help:

Problem
Root drive is full, Amahi crashes. SSHing to box and running 'df -h' shows only significant files in /var/hda/files/drives - the mount location of your external data drives.

Even though you are mounting external drives at /var/hda/files/drives over a folder in this location, there could still be files in the underlying file system. In my case from a Greyhole sync when a new external drive wasn't properly mounted. With the data drives mounted it's difficult to tell what's underneath.

Verify
  • Disable Greyhole
  • Add 'nofail' as an argument to fstab for external data drives so Fedora doesn't hang on boot without them
  • Shut down the server and disconnect data drives and reboot
  • If there is still data accessible in /var/hda/files/drives then you likely have have your cause for why your boot is full (you could also simply unmount the external drives but I wanted to know for sure)
Fix
  • Log in to Amahi web UI and create a new (non Greyhole) share e.g. 'temprecovery'
  • Move the data out of the boot drive and on to your temp share over SSH e.g. mv /var/hda/files/drives/your_disk/gh /var/hda/files/temprecovery/gh
  • On the network, back up your files, then delete them from the share. You can check later if you need them, but it's always best to have a backup.
  • On the Amahi web UI: Check out your recovered space under Disk->Partition. Delete the temp share you created.
  • Turn off the server, reconnect your drives, turn on it on again, enable Greyhole and profit.
  • You will want to edit the 'nofail' argument back out of fstab because if for some reason a data drive doesn't mount at boot in the future, you don't want to risk files being sent to your internal drive again. So it's probably best for the boot to fail if a data drive doesn't come online.
Last edited by johnny5shared on Sat Jul 09, 2016 7:17 pm, edited 9 times in total.

User avatar
bigfoot65
Project Manager
Posts: 11241
Joined: Mon May 25, 2009 4:31 pm

Re: Root full, so I moved the landing zone. Root is still full.

Postby bigfoot65 » Sat Jul 09, 2016 9:29 am

Happy to hear the issue is finally resolved.

Will mark as resolved.

Will add this info to the wiki troubleshooting area for Greyhole.
ßîgƒσστ65
Applications Manager

Who is online

Users browsing this forum: No registered users and 1 guest