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

add support to destroy pool directly #957

Open
yizhanglinux opened this issue Feb 14, 2023 · 1 comment
Open

add support to destroy pool directly #957

yizhanglinux opened this issue Feb 14, 2023 · 1 comment
Assignees

Comments

@yizhanglinux
Copy link

I'm trying to destroy pool directly, but I've to destroy filesystem first, could we add support for such option?
Like add --force option?

[root@storageqe-62 ~]# stratis pool list
Name                           Total / Used / Free    Properties                                   UUID   Alerts
olympic         186.31 GiB / 1.13 GiB / 185.18 GiB   ~Ca,~Cr, Op   9f7343ef-6cce-452a-bedb-8079e5d95046         
stratis_howto       1.46 TiB / 1.78 GiB / 1.45 TiB   ~Ca,~Cr, Op   0a2ff1a5-dcb8-4d1e-8f3d-1c59fe92db35  
[root@storageqe-62 ~]# stratis pool destroy olympic
Execution failed:
stratisd failed to perform the operation that you requested. It returned the following information via the D-Bus: ERROR: filesystems remaining on pool. 

[root@storageqe-62 ~]# stratis daemon version
3.4.4
@mulkieran
Copy link
Member

Part of our design is to not add a --force option anywhere. If we override any safety mechanism, the specific mechanism being overridden must be specified. An example of a specific kind of force option is the option, --trust-url.

For the filesystems, we have always taken the position that the user must umount the filesystem themselves.

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

3 participants