gocryptfs - Mirror of gocryptfs source code on Github

Age	Commit message (Collapse)	Author
2019-01-04	fsck: Do not show files/directories without access permissions as corrupt.	Sebastian Lackner
	When running as a regular user, error EACCES does not necessarily mean that the file/directory/xattr is corrupt, but just that we do not have sufficient access permissions. Add a hint that running as root can be used to check everything. Fixes: https://github.com/rfjakob/gocryptfs/issues/309
2018-12-27	Assorted spelling fixes.	Sebastian Lackner
	Mostly detected with the 'codespell' utility, but also includes some manual grammar fixes.
2018-08-15	fsck: skip already-seen hard-linked files	Jakob Unterwurzacher
	We may hit files several times due to hard links. Only check the contents once.
2018-08-15	fsck: don't print corse corruption offset	Jakob Unterwurzacher
	The exact ciphertext block number (4KiB granularity) is already printed in the doRead message. Don't cause confusion by printing the 128KiB-granularity offset as well. doRead 767: corrupt block #4: stupidgcm: message authentication failed fsck: error reading file "pa/d7/d14/f10c" (inum 767): 5=input/output error
2018-07-23	fsck: print inode number on file read error	Jakob Unterwurzacher
	This makes it possible to find the file without mounting the fs.
2018-07-15	fsck: add debug output (enabled via -debug)	Jakob Unterwurzacher
	Turn the commented-out fmt.Printf into debug output via the tlog infrastructure.
2018-07-01	fsck: handle sparse files efficiently, fix xfstests generic/285	Jakob Unterwurzacher
	If we encounter a 128KB block of zeros, try to skip to the next data section by calling File.SeekData(). This fixes xfstests generic/285, which creates a 17TB sparse file, and runs fsck afterwards. Without this optimization, fsck would take ages.
2018-07-01	fsck: get rid of channel read closures	Jakob Unterwurzacher
	Create proper functions instead to declutter the logic.
2018-07-01	fsck: rename "CorruptItems" channel to "MitigatedCorruptions"	Jakob Unterwurzacher
	Make it clear that this channel is only used to report corruptions that are transparently mitigated and do not return an error to the user.
2018-07-01	fsck: suppress "no problems found" when running quiet	Jakob Unterwurzacher
	Passing "-q" now disables the "fsck summary: no problems found\n" message.
2018-04-03	fsck: report skipped corrupt files	Jakob Unterwurzacher
	OpenDir and ListXAttr skip over corrupt entries, readFileID treats files the are too small as empty. This improves usability in the face of corruption, but hides the problem in a log message instead of putting it in the return code. Create a channel to report these corruptions to fsck so it can report them to the user. Also update the manpage and the changelog with the -fsck option. Closes https://github.com/rfjakob/gocryptfs/issues/191
2018-04-02	fsck: add xattr support	Jakob Unterwurzacher
	With testcases.
2018-04-02	fsck: clean up log output	Jakob Unterwurzacher
	Make sure we get only 1 warning output per problem. Also, add new corruption types to broken_fs_v1.4.
2018-04-02	fsck: sort files alphabetically	Jakob Unterwurzacher
	This makes fsck runs deterministic.
2018-04-02	fsck: add initial implementation	Jakob Unterwurzacher
	Most corruption cases except xattr should be covered. With test filesystem. The output is still pretty ugly. xattr support will be added in the next commits.
2018-04-01	main: add "-fsck" flag	Jakob Unterwurzacher
	The fsck operation is not yet implemented, this commits just adds the flag and improves cli flag handling.