Greyhole problems

[rhubarb]

Hi
I have a number of Greyhole related problems. My storage pool is 2 ESATA drives on a deltaco toaster connected to the HDA by USB.

1) unmounted drives. The USB drives dont seem to be mounting automatically at system boot. If I access them using File Browser then this fixes the problem and Greyhole behaves better

2) HDA log in /var/log :- "The directory at /media/500GB_2/gh doesn't exist" "You should de-select, then re-select this partition...". This is probably related to problem 1)

3) locked files. HDA log in /var/log:- "File is locked by another process" "Only locked files operations pending". Dont know why I get this or how to fix it

4) access problems. I can access the files using Samba but another user cannot due to No permissions. I have created the users in HDA and assigned All Users Writable access to the Shares

Any help appreciated

Peter
Any help apreciated

[cburner]

SSH into the hda and run

Code: Select all

cat /etc/fstab

and post the results here.

[gboudreau]

You should not include anything found in /media in your storage pool.
The directories in that folder are auto-mounted by a Gnome session, which means you need to login on your server for them to become available.
This is also why you're the only one who can write in your shares.
See this page: http://wiki.amahi.org/index.php/Shares_troubleshooting
The second bullet point near the top.

Locked files is usually normal. It means a program is currently using files on your shares. Greyhole is telling you it knows those file changed, but that it can't work on them yet, since another program is still using them.
"Only locked files operations pending." means that all the tasks that are pending for Greyhole are such locked files, and thus, it has nothing to do but wait, so it waits.
There's nothing for you to do about that.

[rhubarb]

Hi
I have moved my 2 USB drives from /media to /mnt by following the instructions here http://myubuntublog.wordpress.com/2009/ ... e-at-boot/. These instructions seem a bit simpler then the Amahi instructions. I hope they are sufficient. See the 2 lines I added at the bottom of /etc/fstab

Code: Select all

[peter@cutting ~]$ cat /etc/fstab # # /etc/fstab # Created by anaconda on Wed May 19 13:19:38 2010 # # 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 # /dev/mapper/vg_cutting-lv_root / ext4 defaults 1 1 UUID=1b355599-03a1-4b95-9c62-a76f75ea3df4 /boot ext4 defaults 1 2 /dev/mapper/vg_cutting-lv_swap swap swap defaults 0 0 tmpfs /dev/shm tmpfs defaults 0 0 devpts /dev/pts devpts gid=5,mode=620 0 0 sysfs /sys sysfs defaults 0 0 proc /proc proc defaults 0 0 # added by pcg /dev/sdc1 /mnt/500GB_1 ext4 auto,user,rw,exec 0 0 /dev/sdb1 /mnt/500GB_2 ext4 auto,user,rw,exec 0 0

I now do not have to login to the HDA to get the USB drives to mount. So that is an improvement.

However I still cannot access the Shares from *another* username (ie not peter). I can connect to the shares and see the directories but not the files. I checked the mount points

[peter@cutting mnt]$ ls -al
total 16
drwxr-xr-x 4 root root 4096 2010-08-23 21:01 .
dr-xr-xr-x 24 root root 4096 2010-08-25 07:16 ..
drwx------ 5 peter peter 4096 2010-08-23 21:17 500GB_1
drwx------ 6 peter peter 4096 2010-08-23 21:18 500GB_2

maybe it is the permissions (owner everything)? I changed them to owner and group everything (chmod 770 *) but that did not help so I tried chmod 777 * and other users now have access. But maybe this is stilll not optimal. What is the correct owner/permissions for the the mount points

Peter

PS I have a script to connect to the Shares which might prove useful:-

Code: Select all

net use * /delete Y net use p: \\hda\Music password /user:sambapeter

[gboudreau]

There are good reasons why we have our own wiki page on how to add secondary hard drive, and we don't just forward you to the hundreds of already existing pages that do something similar.

You're fstab should not identify your drives using the /dev/sdX# nomenclature; they should be identified using their UUID (see your /boot device mount in there).
This will prevent problems down the road, if you even connect your drives differently / in different ports.

For permissions: Try to create a new folder and a new files inside it, from a remote computer. Wait a minute, then look at the owner and permissions of the files it created:

Code: Select all

ls -l /mnt/500GB_*/gh/share_name/folder_name/

For example, you could create a "test" folder in your Music share, then a "testfile" file inside it.

Code: Select all

ls -l /mnt/500GB_*/gh/Music/test/

That will show you what owner, group owner, and permissions your folders and files should have.

Then, to fix (I'll user petersamba as owner, users as owner group, 664 for files permissions, and 775 for folders permissions in the example below; your ):

Code: Select all

chown -R petersamba:users /mnt/500GB_*/gh/* find /mnt/500GB_*/gh/* -type f -exec chmod 664 {} \; find /mnt/500GB_*/gh/* -type d -exec chmod 775 {} \;

[rhubarb]

Hi
I will fix the device setup when i have time.

Thanks for the scripts I also had to run this to get access:-

Code: Select all

sudo find /var/hda/files/* -type d -exec chmod 775 {} \;

not sure if 775 is optimal

Peter

[gboudreau]

775 is the default for Amahi shares, with group owner "users".
That means all your amahi users should be able to read and write to your shares.

If you want to limit write access for some users, you can do that in Samba config, by editing your shares in the Amahi dashboard, in the Setup > Shares page.

[rhubarb]

Hi
I have now (hopefully) changed my config to use device UUIDs so that my USB drives are correctly mounted

I had problems following the Wiki cos it is rather complicated. Firstly I unmounted the incorrectly mounted drives:-

Code: Select all

sudo umount /dev/sdb1 sudo umount /dev/sdc1

I expcted hda-diskmount would tell me the UUIDs but I got problems:-

Code: Select all

[peter@cutting ~]$ sudo hda-diskmount [sudo] password for peter: **************************************************************** /usr/sbin/hda-diskmount: line 222: pmount: command not found Ignoring /dev/sda1 - already mounted Ignoring /dev/sda1 - already in /etc/fstab as UUID=1b355599-03a1-4b95-9c62-a76f75ea3df4 **************************************************************** No usable Linux, Windows or Mac partitions found on your disks. [peter@cutting ~]$

But this command gave me the UUIDs

Code: Select all

[peter@cutting ~]$ ls -l /dev/disk/by-uuid/ total 0 lrwxrwxrwx 1 root root 10 2010-09-01 21:00 1b355599-03a1-4b95-9c62-a76f75ea3df4 -> ../../sda1 lrwxrwxrwx 1 root root 10 2010-09-01 21:00 4cedca69-7aef-402c-9800-1ce5681e0305 -> ../../dm-1 lrwxrwxrwx 1 root root 10 2010-09-01 21:00 7b9b4953-13a8-4708-9257-b9760649fb36 -> ../../dm-0 lrwxrwxrwx 1 root root 10 2010-09-01 21:00 8367a9e0-5a47-4ad4-ad59-815251b563cd -> ../../sdb1 lrwxrwxrwx 1 root root 10 2010-09-01 21:00 b9167bee-60f1-481e-bcd0-a6f53ebc2149 -> ../../sdc1 [peter@cutting ~]$

which I used to modify /etc/fstab:-

Code: Select all

UUID=b9167bee-60f1-481e-bcd0-a6f53ebc2149 /mnt/500GB_1 ext4 auto,user,rw,exec 0 0 UUID=8367a9e0-5a47-4ad4-ad59-815251b563cd /mnt/500GB_2 ext4 auto,user,rw,exec 0 0

Seems to work but I am not totally sure. I suppose I could still be using the old setup. So I am wondering how do I tell that the drives are actually now mounted using the UUIDs

Peter

[gboudreau]

Code: Select all

sudo umount /mnt/500GB_1 sudo umount /mnt/500GB_2 ls -la /mnt/500GB_1 ls -la /mnt/500GB_2 sudo mount -a

Make sure the ls -la commands show empty directories, then repeat the ls -la commands to make sure your drives are re-mounted. If they are, if means the values you have in your fstab files are correct.

[rhubarb]

Hi
interestingly there was a rogue diectory in #2 mount point called gh. Inside gh was .gh_graveyard and inside that was the share dirs etc.

I tried deleting all this but was not successful. It is very weird. As I deleted, directories and files appeared out of nowhere!. After 30mins of rm -rf in a depth-first fashion I gave up.

I have done a fsck as part of a reboot. No help

stuck
Peter