Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mount sdfs does now work after changing basepath #53

Open
GoogleCodeExporter opened this issue Mar 16, 2015 · 0 comments
Open

mount sdfs does now work after changing basepath #53

GoogleCodeExporter opened this issue Mar 16, 2015 · 0 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1.Install ubuntu 12.04 system with fuse and sdfs.
2.Create a volume and mount.Works fine. All dirs in /opt/sdfs is fine.
3.Next change basepath and then create a new volume
Eg:mkfs.sdfs --volume-name=newvol2 --volume-capacity=10MB --base-path /mnt/sdfs
4.mount.sdfs -v newvol2 -m /media/sdfs 
5.cp file to /media/sdfs. It says disk full and df-h show 0 size for / ls -l 
/media/
6.Go back and create volume under /opt/sdfs now and mount, issue in step 5 
recurs.
7. I notice the hashtables and chunkstore files dirs are created but all files 
in it becomes 0 size. It looks like some corruption on fs


What is the expected output? What do you see instead?
Should be able to copy files without error "no place on disk"

What version of the product are you using? On what operating system?
ubuntu12.04,sdfs 1.1.5


Please provide any additional information below.

Original issue reported on code.google.com by [email protected] on 13 Jul 2012 at 1:38

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant