Adopting the solution for resizing root from openwrt expand_root guide #65

Closed
lee.miller wants to merge 3 commits from lee.miller/openwrt:files into main
Collaborator

Hi!

While trying to adopt armbian script for resizing root I found this. Trying to adopt it. Currently having a problem with resizing the filesystem.

Hi! While trying to adopt armbian script for resizing root I found [this](https://openwrt.org/docs/guide-user/advanced/expand_root). Trying to adopt it. Currently having a problem with resizing the filesystem.
lee.miller added 1 commit 2023-12-05 03:09:04 +01:00
Owner

Wow, this looks great! However I'm not fully sure I need it anymore. Can you maybe not spend more time on this for now?

Wow, this looks great! However I'm not fully sure I need it anymore. Can you maybe not spend more time on this for now?
Author
Collaborator

Wow, this looks great! However I'm not fully sure I need it anymore. Can you maybe not spend more time on this for now?

OK, the deadlock in #60 makes me switching tasks.

> Wow, this looks great! However I'm not fully sure I need it anymore. Can you maybe not spend more time on this for now? OK, the deadlock in #60 makes me switching tasks.
lee.miller force-pushed files from 5c990c3fcd to e107bcbe92 2023-12-05 23:26:24 +01:00 Compare
lee.miller changed title from WIP: Adopting the solution for resizing root from openwrt expand_root guide to Adopting the solution for resizing root from openwrt expand_root guide 2023-12-05 23:26:54 +01:00
Owner

If you have extra time, please change the scripts to only resize if root is mmcblk. I don't need the resizing on NVMe, even though the NVMe root doesn't work yet.

If you have extra time, please change the scripts to only resize if root is mmcblk. I don't need the resizing on NVMe, even though the NVMe root doesn't work yet.
Author
Collaborator

If you have extra time, please change the scripts to only resize if root is mmcblk. I don't need the resizing on NVMe, even though the NVMe root doesn't work yet.

OK, it's not gonna take much time

> If you have extra time, please change the scripts to only resize if root is mmcblk. I don't need the resizing on NVMe, even though the NVMe root doesn't work yet. OK, it's not gonna take much time
lee.miller added 1 commit 2023-12-06 00:38:59 +01:00
Author
Collaborator

There is something I missed here. After about a week of using the card with expanded root I see following messages in console:

Failed chdir '/root': Invalid argument
Your JFFS2-partition seems full and overlayfs is mounted read-only.
Please try to remove files from /overlay/upper/... and reboot!
There is something I missed here. After about a week of using the card with expanded root I see following messages in console: ``` Failed chdir '/root': Invalid argument Your JFFS2-partition seems full and overlayfs is mounted read-only. Please try to remove files from /overlay/upper/... and reboot! ```
Owner

That's strange, it shouldn't be using jffs2. It should be using squashfs+f2fs.

That's strange, it shouldn't be using jffs2. It should be using squashfs+f2fs.
Author
Collaborator

That's strange, it shouldn't be using jffs2. It should be using squashfs+f2fs.

It's a static message: https://github.com/openwrt/openwrt/blob/main/package/base-files/files/etc/profile#L6

> That's strange, it shouldn't be using jffs2. It should be using squashfs+f2fs. It's a static message: https://github.com/openwrt/openwrt/blob/main/package/base-files/files/etc/profile#L6
Owner

After thinking about this, I don't think this is needed. If the filesystem size is too big, running sysupgrade will fail as it would need to fit everything into RAM. So instead we should focus on creating such images that don't need much additional space in the F2FS partition.

After thinking about this, I don't think this is needed. If the filesystem size is too big, running `sysupgrade` will fail as it would need to fit everything into RAM. So instead we should focus on creating such images that don't need much additional space in the F2FS partition.
PeterSurda closed this pull request 2024-01-26 01:37:11 +01:00

Pull request closed

Sign in to join this conversation.
No reviewers
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Sysdeploy/openwrt#65
No description provided.