Skip to content

Bump go-diskfs pin to current master - #25

Merged
deitch merged 1 commit into
diskfs:mainfrom
eriknordmark:bump-go-diskfs
Aug 4, 2026
Merged

Bump go-diskfs pin to current master#25
deitch merged 1 commit into
diskfs:mainfrom
eriknordmark:bump-go-diskfs

Conversation

@eriknordmark

Copy link
Copy Markdown
Contributor

Moves the go-diskfs pin from v1.9.4-0.20260710070848-6793ed76fd75 to the
current master tip, v1.9.5-0.20260803113315-a6099fdbe455.

Four upstream fixes come in, all on filesystem paths the resizer drives when
it copies and grows source filesystems:

No source changes are needed; only go.mod/go.sum move.

Picks up four upstream fixes since the last pin: correct extent-tree
splits and internal-node spans for large fragmented ext4 files, real
error causes on failed ext4 directory reads instead of a bare "not
found", and FAT32 handling of zero-length files and dot-leading
filenames. The ext4 and FAT32 paths are the ones the resizer exercises
when it copies and grows source filesystems, so these land directly
under partitionresizer's own copy/grow behavior.

Signed-off-by: eriknordmark <erik@zededa.com>
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@eriknordmark

Copy link
Copy Markdown
Contributor Author

@deitch PTAL — straight pin bump to go-diskfs master (a6099fd), picking up #412/#419/#420/#421. Full go test ./... passes locally.

@deitch
deitch merged commit b362ce3 into diskfs:main Aug 4, 2026
9 checks passed
@eriknordmark
eriknordmark deleted the bump-go-diskfs branch August 4, 2026 11:40
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

Successfully merging this pull request may close these issues.

2 participants