Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[SUPPORT] broken links #674

Closed
gcb opened this issue Dec 28, 2024 · 1 comment
Closed

[SUPPORT] broken links #674

gcb opened this issue Dec 28, 2024 · 1 comment

Comments

@gcb
Copy link

gcb commented Dec 28, 2024

My encrypted directory start to show some broken links:

lrwxrwxrwx 1 1000 1000 47 2009-07-02 02:33 YiMtLX50mSoFzM4pZHFdlVUC/-5BF9PdQyZqnezr8dvahZvs8/NDAu-mrufu-ZTmJDaBPLRlQKv39B4bcEw-2eB5jwsa-2VIskERbI97Zgk7JqFuW8,,3/UI6GM26otSl7cbE8gaUvlHzW/JVzNodtmEbbpChbgjkjLQXuL/B3LLXe83B7T6z9XLzCMco8h8/BsBxtZl98dXSA6PABszLnrGG -> +gyAh6ImeUIwUTXStj4TJXePetbs,uPJt7-wWL7-GjP,3y-

The dir containing these broken links (2) have modification date of 2012, the links have 2009, which is the date the volume was created.

encfs version 1.9.5, Linux 6.12.6

it sits on this ext4 partition

Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype extent 64bit flex_bg sparse_super large_file huge_file dir_nlink extra_isize metadata_csum
Filesystem flags:         signed_directory_hash 
Default mount options:    user_xattr acl
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              115965952
Block count:              463834368
Reserved block count:     23191718
Overhead clusters:        7562021
Free blocks:              250206903
Free inodes:              115641059
First block:              0
Block size:               4096
Fragment size:            4096
Group descriptor size:    64
Reserved GDT blocks:      1024
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         8192
Inode blocks per group:   512
Flex block group size:    16
Filesystem created:       Thu Jul  8 01:20:42 2021
Last mount time:          Sat Dec 28 14:16:32 2024
Last write time:          Sat Dec 28 14:16:36 2024
Mount count:              96
Maximum mount count:      1
Last checked:             Thu Jul  8 01:20:42 2021
Check interval:           0 (<none>)
Lifetime writes:          833 GB
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:               256
Required extra isize:     32
Desired extra isize:      32
Journal inode:            8
Default directory hash:   half_md4
Journal backup:           inode blocks
Checksum type:            crc32c
Checksum:                 0x8e8ebc0d

This always lived on RAID with mirror/parity. from 2009, and then moved to fresh new storage, also with RAID with mirror/parity in 2012, and again in 2021... Was about to upgrade storage medium again today and noticed these.

RAID scrubs never showed problems all this time.

The encFS volume is assembled once a month or so and a few files added, almost never files are changed, but might happen. Deletions are also very rare.

Should I be worried?

@gcb
Copy link
Author

gcb commented Dec 28, 2024

User error :)

I noticed those broken links when rsync'ing a backup and it complained about them. Just redid the backup but this time using the unlocked/open mount.

The broken links are actual broken links, which were stored just fine! Previously I did the backups with cp -a, not using rsync and it is picky about copying those.

@gcb gcb closed this as completed Dec 28, 2024
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

No branches or pull requests

1 participant