<feed xmlns='http://www.w3.org/2005/Atom'>
<title>gocryptfs/tests/fsck, branch v2.0-beta2</title>
<subtitle>Mirror of gocryptfs source code on Github</subtitle>
<id>http://nuetzlich.net/cgit/gocryptfs/atom?h=v2.0-beta2</id>
<link rel='self' href='http://nuetzlich.net/cgit/gocryptfs/atom?h=v2.0-beta2'/>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/'/>
<updated>2020-07-19T21:03:47+00:00</updated>
<entry>
<title>v2api: fsck: use a temporary mount</title>
<updated>2020-07-19T21:03:47+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2020-07-19T21:03:47+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=8915785acf7e6e7908b32103406620f243093931'/>
<id>urn:sha1:8915785acf7e6e7908b32103406620f243093931</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>Add CodeLingo Tenet to fix missing close file</title>
<updated>2019-04-10T11:33:58+00:00</updated>
<author>
<name>leilaes</name>
</author>
<published>2019-04-10T07:43:34+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=cc0a603ef8a691b01fbd0f6a99e7d4e1d36608f7'/>
<id>urn:sha1:cc0a603ef8a691b01fbd0f6a99e7d4e1d36608f7</id>
<content type='text'>
</content>
</entry>
<entry>
<title>fsck: handle sparse files efficiently, fix xfstests generic/285</title>
<updated>2018-07-01T19:48:51+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2018-07-01T17:14:00+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=2d68b06f9dab66b2a0a6c29c8d5450e2b1d43fae'/>
<id>urn:sha1:2d68b06f9dab66b2a0a6c29c8d5450e2b1d43fae</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>trezor: add skeleton for Trezor support</title>
<updated>2018-07-01T18:56:04+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2018-06-17T13:25:09+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=c6f6e8ec4d71475a24ebbb0e64f19ad94249efd9'/>
<id>urn:sha1:c6f6e8ec4d71475a24ebbb0e64f19ad94249efd9</id>
<content type='text'>
readpassword.Trezor() is not implemented yet and returns
a hardcoded dummy key.
</content>
</entry>
<entry>
<title>fsck: update testcases with binary xattrs</title>
<updated>2018-05-10T21:26:00+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2018-05-10T21:18:16+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=f7a6f4d46858dcd049bcf671509bdf42e5d26d09'/>
<id>urn:sha1:f7a6f4d46858dcd049bcf671509bdf42e5d26d09</id>
<content type='text'>
</content>
</entry>
<entry>
<title>fsck: add xattr support</title>
<updated>2018-04-02T18:25:59+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2018-04-02T18:25:59+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=8b443c8484f5fdcedbec2a689a7d66d2a277b26e'/>
<id>urn:sha1:8b443c8484f5fdcedbec2a689a7d66d2a277b26e</id>
<content type='text'>
With testcases.
</content>
</entry>
<entry>
<title>fsck: test against example_filesystems</title>
<updated>2018-04-02T16:43:50+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2018-04-02T16:43:50+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=a0fd3eca98218aa7d165080ab20cf234330e5e09'/>
<id>urn:sha1:a0fd3eca98218aa7d165080ab20cf234330e5e09</id>
<content type='text'>
</content>
</entry>
<entry>
<title>fsck: clean up log output</title>
<updated>2018-04-02T16:32:30+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2018-04-02T16:32:30+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=b6c8960b01f9e5366814b0dada57a0b1e6a031d9'/>
<id>urn:sha1:b6c8960b01f9e5366814b0dada57a0b1e6a031d9</id>
<content type='text'>
Make sure we get only 1 warning output per
problem.

Also, add new corruption types to broken_fs_v1.4.
</content>
</entry>
<entry>
<title>fsck: add initial implementation</title>
<updated>2018-04-02T14:38:18+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2018-04-01T19:23:32+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=f28d85fad599ffaef9a8e1f353911c81a6605d2f'/>
<id>urn:sha1:f28d85fad599ffaef9a8e1f353911c81a6605d2f</id>
<content type='text'>
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.
</content>
</entry>
</feed>
