gocryptfs/fsck.go, branch xattr_user_buffer

Use user-provided Listxattr buffer size

2026-02-03T19:28:10+00:00

This huge buffer showed up big time in ./profiling/ls.bash and caused a 2x LS benchmark slowdown. Instead of the fixed-size buffer, use the buffer size hint the user has provided us. We return inaccurate (larger than actual, which should be safe) numbers when the user has provided no buffer (size probe).

Fix a bunch of staticcheck errors

2025-07-07T17:59:35+00:00

Tool-assisted.

fsck: print "Checking filesystem..."

2023-09-17T14:38:50+00:00

From https://github.com/rfjakob/gocryptfs/issues/779 / @jroovy > When using `-fsck`, the command line output looks like this: > > ``` > $ gocryptfs -fsck ENCRYPTED_DIRECTORY > Password: > Decrypting master key > ``` > > However, the user might think it's stuck at decrypting the master > key. Adding extra text showing that fsck is working would be nice, > something like: > > ``` > $ gocryptfs -fsck ENCRYPTED_DIRECTORY > Password: > Decrypting master key > Checking filesystem... > ``` Fixes https://github.com/rfjakob/gocryptfs/issues/779

go mod: declare module version v2

2021-08-23T13:05:15+00:00

Our git version is v2+ for some time now, but go.mod still declared v1. Hopefully making both match makes https://pkg.go.dev/github.com/rfjakob/gocryptfs/v2 work. All the import paths have been fixed like this: find . -name \*.go | xargs sed -i s%github.com/rfjakob/gocryptfs/%github.com/rfjakob/gocryptfs/v2/%

fsck: sort files alphabetically again

2021-08-19T06:34:49+00:00

This makes fsck runs deterministic again. Sorting (commit quoted below) got lost while moving to go-fuse v2 api. commit e6caf56ea4ab10e747aa5dfc0a768cb8176ebe6a Author: Jakob Unterwurzacher Date: Mon Apr 2 16:56:29 2018 +0200 fsck: sort files alphabetically This makes fsck runs deterministic.

fsck: mark temporary mount read-only

2021-06-02T17:32:20+00:00

We don't write during fsck, but somebody else might try to.

fsck: clean up temporary mountpoint

2021-06-02T17:31:55+00:00

We used to leave directories like /tmp/gocryptfs.fsck.104431245 behind. Let's clean up after ourselves.

fsck: redirect go-fuse noise to syslog

2021-05-18T16:38:23+00:00

fsck: make sure we unmount in all cases

2020-10-17T21:03:58+00:00

v2api: fsck: use a temporary mount

2020-07-19T21:03:47+00:00

Directly accessing the Nodes does not work properly, as there is no way to attach a newly LOOKUPped Node to the tree. This means Path() does not work. Use an actual mount instead and walk the tree.