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

Don't create to create btrfs subvolumes that already exist #586

Closed
ghost opened this issue Dec 9, 2016 · 1 comment
Closed

Don't create to create btrfs subvolumes that already exist #586

ghost opened this issue Dec 9, 2016 · 1 comment

Comments

@ghost
Copy link

ghost commented Dec 9, 2016

Jira issue originally created by user sb56637:

Hi, I'm trying to see if I can install openSUSE via Calamares to a BtrFS partition that lets me enable Snapper integration with GRUB2. For that to work, openSUSE expects certain BtrFS sub-volumes to be present. So I pre-created a partition with @ and @/home subvolumes, then used Calamares to try to install onto that partition with the "keep" option. However, it looks like Calamares fails because it still tried to re-create those sub-volumes:

`Boost.Python error in job "mount".
<class 'subprocess.CalledProcessError'>
Command '['btrfs', 'subvolume', 'create', '/tmp/calamares-root-q3kdlt07/@']' returned non-zero exit status 1
Traceback:
File "/usr/lib64/calamares/modules/mount/main.py", line 124, in run
mountpartitions(root_mountpoint, partitions)

File "/usr/lib64/calamares/modules/mount/main.py", line 74, in mount_partitions
rootmountpoint + '/@'])

File "/usr/lib64/python3.4/subprocess.py", line 558, in check_call
raise CalledProcessError(retcode, cmd)`

@ghost ghost added the bug label Feb 23, 2017
@abucodonosor abucodonosor changed the title CAL-429: Don't create to create BtrFS sub-volumes that already exist Don't create to create btrfs subvolumes that already exist Sep 18, 2017
@demmm
Copy link
Contributor

demmm commented Sep 13, 2022

This feature request is now well over 6 years old, never a PR submitted for it, time to close. It should be implemented with other, much more recent BTRFS changes requested.

@demmm demmm closed this as completed Sep 13, 2022
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

2 participants