From: Piotr S. <pio...@gm...> - 2011-01-08 23:20:05
|
Hello everyone! So, I'm quite new to MooseFS, I've installed the whole system recently, including master and chunk deamon, etc. The problem I encountered (and can't get through) is most probably the access/permission problem. This is how the situation looks like : I have 3 servers, 1 of them is VPS (what means it has no access to /dev/fuse, nor /dev/loop), 2 are real servers having WAN ip and etc. I decided to use VPS as mfsmaster, and the rest would be chunk servers. I haven't got separate disks, so I used /dev/loop on chunk servers to create 500 MB ext3 file system and mounted it, as it has been described in the manual. # df -m Filesystem 1M-blocks Used Available Use% Mounted on /data/mfsdisk 462 11 428 3% /mnt/mfschunk Now, when I run the master server, and chunks, and on one of them I use so called 'client' (mfsmount) and - everything works : # df -m /data/mfsdisk 462 11 428 3% /mnt/mfschunk mfsmaster:9421 343 0 343 0% /mnt/mfs except of that I can't write to /mnt/mfs. Basically I managed to touch empty files as well as to create empty directories, but no sooner do I echo anything to any files than it gives me an error : No space left on the device. Sometimes it does not say anything, for instance : [root@chunk mfs]# touch file [root@chunk mfs]# echo "test" >> file [root@chunk mfs]# ls -la file -rw-r--r-- 1 999 999 0 Jan 9 00:13 file What I have noticed is that under /mnt/mfschunk (where the pseudo hdd is mounted) there are lots of weird directories. Not sure if I ought to touch them... 00 07 0E 15 1C 23 2A 31 38 3F 46 4D 54 I would very much appreciate any help in this matter. Kind Regards, Peter |