Community Forum

Ask any questions you have about ElasticDrive.
Download available here > http://www.elasticdrive.com

Hi there, thanks for earlier help with e2fsck; it did the trick! I have another question, if you're able to help please?

I'm running version 4.1 of ElasticDrive, backed with S3, and am having a few issues at the moment when writing large files (~60 meg or so) to a mounted s3 partition (not RAID). The application that is writing the data seems to get bored of waiting for the data to be written to S3 and times out. Now, I've done some searching on the old AWS support forum and found mention of a 'cache size' option but can't find it in the documentation. Does this option still exist? I think I basically want to increase it so that files "written" to the partition appear to happen quickly. Do I have the right idea or is there another solution you would suggest?

Thanks for any help!
Mark

Hello.
I do this as root at Amazon Ec2 Fedora 8 32-bit instance:

#yum install fuse fuse-devel python-devel python-ctypes python-fuse
#modprobe fuse
#modprobe nbd
edit /etc/elasticdrive.cfg, write right keys and bucket name


#elasticdrive /etc/elasticdrive.cfg -d
#mkdir -p /mnt/s3dev/ed0
#mke2fs -b 4096 /mnt/s3dev/ed0
At this step I have an error:


So I can't do that 2 commands:
#mkdir /s3
#mount /mnt/s3dev/ed0 /s3 -o loop

and I can't create Elastic Drive.

Can you help me?

Max

Hello,

I am having the same problem with mke2fs as Max above when following your usage & installation instructions.

Has there been any progress or solution to this?

I am running on a x64 FC6 image on EC2. I ran through install no problems, and have modprobe fuse loaded and elasticdrive running, as checked with ps. But I cannot create my mounting filesystem when running:
# mke2fs -b 4096 /mnt/ed0
/mnt/ed0 is not a block special device.
Proceed anyway? (y,n) y
Device size reported to be zero. Invalid partition specified, or
partition table wasn't reread after running fdisk, due to
a modified partition being busy and in use. You may need to reboot
to re-read your partition table

What do I need to do in order to check proper function and/or solve this partition problem?

Any insight is appreciated.

-Chad Heimbecker

Did you format that partition after mounted it? I think you need to format it so that it could become valid filesystem.

The problem he ran into was a missing device node to actually format, I chatted with him on the phone and I have one of our developers looking into the problem. Also when you setup your fuse line to /mnt/ed0, the device itself will be /mnt/ed0/ed0, odd but valid.

Hello,
I do this as root at EC2 Fedora6 64-bit instance. I have updated all the required fuse python
and other related libraries. Installed elasticdrive successfully.

Then ran these commands,

elasticdrive /etc/elasticdrive.ini -d
ps aux | grep elastic
Got my elasticdrive running there. It got my bucket also.

But when I run ls -al /fuse2
I don't see ed0. I think that's why when I try to run this


Not sure what I did wrong and what to do now?
Here is my config,



Any help would be appreciated.

This is the exact same issue we're seeing on some installs, I have one of the developers looking into it to see if it can be reproduced locally. The symptoms are always the same... the ed0 device node is not showing up when ElasticDrive is running. I'll keep you guys posted here.

Hi Pat,

Do you have any updates on the problem, re: ed0 not appearing in the filesystem? I am running ED inside a CentOS 5.2 VMware virtual machine and have seen this problem.

Strangely, when I run ED in foreground mode, the ed0 file appears, but if I use "-d" to make an ED daemon, the file does not appear.

Can I provide anything else (log file, strace output, etc.) to help you troubleshoot the problem?

Regards,
Greg Larkin
http://www.sourcehosting.net/