Fix/improve the btrfs_resize function
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- c
- Domain
- operating-systems
Research direction
Start from the bd_btrfs_resize() function, which the issue names as the place to add a device parameter. Read how it currently calls the btrfs resize command, and check how the btrfs filesystem resize DEV_ID:SIZE form works. Done means a caller can target one device, and a call without a device spreads the requested total size across the file system's devices. The issue has no comments or linked pull request, so ask the maintainers about the intended API before you write code.
Written by the indexing model from the issue text.
Description
In order to resize a btrfs file system one needs to specify sizes of space that should be used on devices used by the btrfs file system. Simply calling btrfs filesystem resize SIZE MNT_POINT only resizes the first device not the whole file system. btrfs filesystem resize DEV_ID:SIZE MNT_POINT resizes a particular device.
Thus we need to add a parameter to bd_btrfs_resize() that will allow callers to specify a device and if none is specified, we need to calculate how much space we need to take from devices used by the file system to get the given total size (as one would expect from such function).
- Dominant language
- C
- Stars
- 137
- Forks
- 64
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 3
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from storaged-project/libblockdev
-
fails to build with libnvme3 (nvme-cli 3.0)Possibly taken @tbzatek claimed this 42 days ago. Open
storaged-project/libblockdev#1211 · 4 comments · 1 assignee ·
-
RFE
Difficulty 3/5 1-2 days Newbie friendliness 35/100
storaged-project/libblockdev#1093 · 3 comments ·
-
Difficulty 4/5 Over a week Newbie friendliness 18/100
storaged-project/libblockdev#1067 ·
-
Difficulty 3/5 Half a day Newbie friendliness 40/100
storaged-project/libblockdev#1060 · 1 comment ·
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 12/100
storaged-project/libblockdev#977 · 1 comment ·
All issues in storaged-project/libblockdev
Similar issues
-
dependency component: oneMKL module: dpclang
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
intel/torch-xpu-ops#5880 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
CVE-2026-111497Open
Difficulty 1/5 Under an hour Newbie friendliness 82/100
fink/fink-distributions#1322 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 83/100
openvehicles/Open-Vehicle-Monitoring-System-3#1563 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100