gocryptfs/fsck.go, branch dependabot/github_actions/actions/checkout-7Mirror of gocryptfs source code on Githubhttp://nuetzlich.net/cgit/gocryptfs/atom?h=dependabot%2Fgithub_actions%2Factions%2Fcheckout-72025-07-07T17:59:35+00:00Fix a bunch of staticcheck errors2025-07-07T17:59:35+00:00Jakob Unterwurzacher2025-07-07T17:54:48+00:00urn:sha1:8f5df19b353e02ffba842fd1b15ccf93da7ee3b4
Tool-assisted.
fsck: print "Checking filesystem..."2023-09-17T14:38:50+00:00Jakob Unterwurzacher2023-09-17T14:38:50+00:00urn:sha1:4ef110f1f3dd6308d88e951aa89dc426d32ad6f1
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 v22021-08-23T13:05:15+00:00Jakob Unterwurzacher2021-08-23T13:05:15+00:00urn:sha1:69d88505fd7f4cb0d9e4f1918de296342fe05858
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 again2021-08-19T06:34:49+00:00Jakob Unterwurzacher2021-08-19T06:22:52+00:00urn:sha1:f3d927e590c1e9fc3a0ef9402d9c83b972981232
This makes fsck runs deterministic again.
Sorting (commit quoted below) got lost while
moving to go-fuse v2 api.
commit e6caf56ea4ab10e747aa5dfc0a768cb8176ebe6a
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Mon Apr 2 16:56:29 2018 +0200
fsck: sort files alphabetically
This makes fsck runs deterministic.
fsck: mark temporary mount read-only2021-06-02T17:32:20+00:00Jakob Unterwurzacher2021-06-02T17:32:20+00:00urn:sha1:8f2be5d93cda2696fce7bc1a3f8a888a19321f09
We don't write during fsck, but somebody else might try
to.
fsck: clean up temporary mountpoint2021-06-02T17:31:55+00:00Jakob Unterwurzacher2021-06-02T17:28:20+00:00urn:sha1:307dfd7f71ee1d72113e2194e9b26a53b9a36c46
We used to leave directories like
/tmp/gocryptfs.fsck.104431245
behind. Let's clean up after ourselves.
fsck: redirect go-fuse noise to syslog2021-05-18T16:38:23+00:00Jakob Unterwurzacher2021-05-18T16:38:23+00:00urn:sha1:0650a512bbf5a49031d47afac538a92e0994757afsck: make sure we unmount in all cases2020-10-17T21:03:58+00:00Jakob Unterwurzacher2020-10-17T21:03:58+00:00urn:sha1:95ea7383f9aeef83e6ce7a06d49d0f24857ef30av2api: fsck: use a temporary mount2020-07-19T21:03:47+00:00Jakob Unterwurzacher2020-07-19T21:03:47+00:00urn:sha1:8915785acf7e6e7908b32103406620f243093931
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.
v2api: enable go-fuse warnings on mount & fsck2020-07-19T10:48:29+00:00Jakob Unterwurzacher2020-07-19T10:48:29+00:00urn:sha1:015a88409086e4a1af60ab85c5b129f909db3e45