8000 Docs: Block devices · Issue #252 · moosefs/moosefs · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Docs: Block devices #252

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.

Sign up for GitHub

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

Jump to bottom
Open
dragon2611 opened this issue May 1, 2019 · 5 comments
Open

Docs: Block devices #252

dragon2611 opened this issue May 1, 2019 · 5 comments
Labels
feature Idea of a new feature to make MooseFS even better! :)

Comments

@dragon2611
Copy link

Is it possible to get better documentation around block devices, does it require the master to allow / to be mounted as I can't see a way of allowing for example /blockd to be used for block devices.

If i only allow a mount that is a subfolder mfsbdev start seems to fail.
@acid-maker
Copy link
Member

Now blockdevice daemon always use '/' as a root path when it connects to master. So this is for me "feature request" :)

@acid-maker acid-maker added the feature Idea of a new feature to make MooseFS even better! :) label May 6, 2019
acid-maker added a commit that referenced this issue May 6, 2019
@acid-maker
(nbd) added optios for specifying subfolder on MFS for block devices …
e978091 
…(issue #252)
@acid-maker
Copy link
Member

I've just added option '-S' for block devices for specifying master subfolder.

All client modules (mfsmount,mfsbdev and also libmfsio) use the same export rules defined in 'mfsexports.cfg', so yes - mfsbdev has to be allowed in mfsexports.cfg in the same way as mfsmount.

@dragon2611
Copy link
Author

@acid-maker extremely minor but there's a typo in the change-log for your commit.

@acid-maker
Copy link
Member

@dragon2611 - thanks :)

@asyslinux
Copy link

Hm, I do not understand about mfsbdev.

If I use standard mfsmount with fuse, then I simply mount moosefs , do work, change replica goals, etc...

But I look manual about mfsbdev, and dont understand.

Standard example:
mfsmaster:9421 3.4T 121G 3.3T 4% /var/cluster - this is mounted moosefs

Mfsbdev can create block device from entire MooseFS and how to work with this?

I look only option about file -f (where this file need stay? in /var/cluster/ mounted MooseFS)

Or mfsbdev its a feature for mount different native file from other native file system from separate hdds (eg ext4) inside a subfolder in /var/cluster/block , where block = file on /dev/sde4 (ext4) ?

Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature Idea of a new feature to make MooseFS even better! :)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@dragon2611 @acid-maker @asyslinux
0