I stumped myself twice on this problem. Here's hoping I won't encounter a third.
SeaweedFS requires a separate process to be executed for mounting each volume, such as the following:
sudo ./weed volume -dir=”/data/seaweed/data1” -max=5 -mserver=”localhost:9333” -port=8080 &
There is actually a problem with the above command. Good for you if you're observant enough. I failed to notice it months after I first spotted it, when I had to revisit it.
SeaweedFS will return with "volume.go:149 Check Data Folder(-dir) Writable ”/data/seaweed/data1” : stat ”/data/seaweed/data1”: no such file or directory" from the above instruction.
I found this issue, but it was not helpful. I tried to chmod the folder (again), this time to 777 even (this is just a dev env) to no avail. I revisited the exception thrown from Retracing my steps, I returned to their source code on github once more. That helped to jog my memory a little more.
It was the auto-correct from my Outlook. I'd copied the command from my older email. Inclusive of the non-Linux quotation symbols. I resolved it and decided to email myself once more with the updated command this time round, to be sure.
sudo ./weed volume -dir=/data/seaweed/data1 -max=5 -mserver=localhost:9333 -port=8080 &
I figured, why make thing pain when thing simple work?
No comments:
Post a Comment