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

Creating a backstore fails, "Could not create _Backstore in configFS" #139

Closed
jamespharvey20 opened this issue Jun 27, 2019 · 1 comment
Closed

Comments

@jamespharvey20
Copy link

I've successfully used targetcli-fb off and on for years. I last used it in January, but no longer needed it, so removed all shares. I was using v2.1.fb49 then and now. I've also tried current git, 85031ad. I'm also running python-rtslib-fb 2.1.fb69, using python3, and python-configshell-fb 1.1.fb25, also using python3.

# systemctl start target
# targetcli-fb
targetcli shell version 2.1.fb49
Copyright 2011-2013 by Datera, Inc and others.
For help on commands, type 'help'.

/> cd /backstores/block
/backstores/block> create <NAME> /dev/lvm/<BLOCK-DEVICE-NAME>
Could not create _Backstore in configFS

I'm running Arch Linux, which is a rolling release, so basically has the current version of everything, including kernel 5.1.15.

Unfortunately, as I didn't try using it between January and now, I don't know when it would have stopped working or what would have triggered it. I think it has to be one of its dependencies that changed, requiring an update for targetcli-fb.

I did see #130

I don't know if it's related at all. I never had to do anything with mounting before. I do see:

mount | grep configfs
configfs                          /sys/kernel/config                 configfs    (rw,nosuid,nodev,noexec,relatime)

And, within there, is pci_ep, rdma_cm, and target.

I tried remounting /sys/kernel/config/, based on the other issue, which had no effect. Nothing has ever been mounted at /config/.

@jamespharvey20
Copy link
Author

Upgrading to python-configshell-fb 1.1.26 and targetcli-fb 2.1.50 fixes the issue.

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

No branches or pull requests

1 participant