LinuxFS

SSHFS

Für schnelleren Zugriff Kompression ausschalten und sparsamen Cipher arcfour verwenden.
Blazingly fast sshfs

/etc/ssh/sshd_config:
Ciphers chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,arcfour

/etc/auto.sshfs:
Rechner	-fstype=fuse,allow_other,compression=no,Ciphers=arcfour        :sshfs\#user@rechner.lan\:/

EXT4

Die Metadata Prüfsummen sollten auf 32 Bit erweitert werden.

Here's one: when ext4 is running on flaky hardware, it gives hard to
diagnose errors that at the first glance don't look like disk corruption at
all: mostly, you get random segfaults.  Btrfs on the other hand immediately
informs you what's wrong.

Failure mode on this relatively frequent problem is quite nasty.

But, not all is lost.  ext4 has recently grown metadata (only) checksums,
and having them protects you from worst kinds of corruption.  As is, data
corruption is localized, metadata breakage can kill the whole filesystem.
You also get a random chance to be notified of problems with disk cable/
controller/etc, as a bad write or read will hit a metadata block sooner or
later.

Thus, if you created your filesystem with mkfs.ext4 older than
stretch/ascii, it's vital that you do the following, on an unmounted
filesystem (ie, need to boot from alternate media if it's /):

resize2fs -b $DEV
tune2fs -O metadata_csum $DEV
e2fsck -fD $DEV

There's a caveat that such a filesystem can't be mounted with kernels prior
to 3.6 (I found this the hard way, after mkfs-ing on unstable), but by now,
this shouldn't be a concern as even jessie has 3.16.

und

https://ext4.wiki.kernel.org/index.php/Ext4_Disk_Layout clarifies what
this specific command sequence is about: the '64bit' feature and its
connection to block size and to the metadata checksum option:

  By default a filesystem can contain 2^32 blocks; if the '64bit'
  feature is enabled, then a filesystem can have 2^64 blocks.
  [...]

  Some [hisorical ext4] data structures did not have space to fit a full
  32-bit checksum, so only the lower 16 bits are stored. Enabling the
  64bit feature increases the data structure size so that full 32-bit
  checksums can be stored for many data structures. However, existing
  32-bit filesystems cannot be extended to enable 64bit mode, at least not
  without the experimental resize2fs patches to do so.

One gathers that the 'experimental resize2fs patches' have been merged
since the above was written.

  Existing filesystems can have checksumming added by running tune2fs -O
  metadata_csum against the underlying device.
  [...]

So, 'resize2fs -b [devicename]' turns on the filesystem's 64bit feature,
rewriting ext4 metadata in a way that makes adequate room for storing
full 32-bit checksums on all file metadata structures instead of just
the lower 16 bits -- with the minor drawback of making the ext4
filsystem unmountable by systems with pre-3.6 kernels.  Having done this
house-cleaning, now you can do the second command that toggles on the
metadata checksum option.  Last, 'fsck.ext4 -D [devicename]' 'optimises'
(reindexes, or sorts and compresses) all directories.