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

WebUI feature request: grow btrfs filesystem on expanded Virtual Disk #2808

Open
Hooverdan96 opened this issue Mar 15, 2024 · 0 comments
Open

Comments

@Hooverdan96
Copy link
Member

Hooverdan96 commented Mar 15, 2024

Reported by @goremaker on the Rockstor forum: (https://forum.rockstor.com/t/rockstor-not-recognizing-expanded-storage-size/9340)

When using Rockstor in a VM setup (Proxmox, Virtualbox, etc.) and an existing btrfs storage disk is increased in size, there is currently no option to automatically or manually increase the filesystem to the enlarged portion of the disk. This was not considered a valid scenario originally (due to the design intent of offering Rockstor as an appliance with its own dedicated hardware, aka built on bar metal).

However, as observed in the forum in this and other threads, users are starting to multi-purpose server hardware (due to increased capabilities/performance that has become more affordable compared to 10 years ago) which can be addressed by virtualizing appliances like Rockstor.

The current approach to expand a filesystem to the full disk after a resizing of said virtual disk is to execute this at the command line using

btrfs filesystem resize <devid> max <mnt>

as described here: btrfs filesystem resize

Request is to incorporate this into the WebUI:

  • recognize the changed device size on the disk page
  • allow for expansion of filesystem to increased size
  • optional: create a workflow that allows for automatic resizing of the filesystem, if the underlying device is "grown"
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