mirror of
https://github.com/kdave/btrfs-progs
synced 2024-12-22 22:23:32 +00:00
65181c273e
The original idea of not doing DUP on SSD was that the duplicate blocks get deduplicated again by the driver firmware. This was in 2013, years ago. Then it was speculative and even nowadays we don't have much reliable information from vendors what optimizations are done on the drive level. After the year there's enough information gathered by user community and there's no simple answer. Expensive drives are more reliable but less common, for cheap consumer drive it's vice versa. The characteristics are described in more detail in manual page btrfs(5) in section "SOLID STATE DRIVES (SSD)". The reasoning is based on numerous reports on IRC and technical difficulty on mkfs side to do the right decision. The default is chosen to be the safe option and up to user to change that based on informed decision. Issue: #319 Signed-off-by: David Sterba <dsterba@suse.com> |
||
---|---|---|
.. | ||
asciidoc.conf | ||
btrfs-balance.asciidoc | ||
btrfs-check.asciidoc | ||
btrfs-convert.asciidoc | ||
btrfs-device.asciidoc | ||
btrfs-filesystem.asciidoc | ||
btrfs-find-root.asciidoc | ||
btrfs-image.asciidoc | ||
btrfs-inspect-internal.asciidoc | ||
btrfs-ioctl.asciidoc | ||
btrfs-man5.asciidoc | ||
btrfs-map-logical.asciidoc | ||
btrfs-property.asciidoc | ||
btrfs-qgroup.asciidoc | ||
btrfs-quota.asciidoc | ||
btrfs-receive.asciidoc | ||
btrfs-replace.asciidoc | ||
btrfs-rescue.asciidoc | ||
btrfs-restore.asciidoc | ||
btrfs-scrub.asciidoc | ||
btrfs-select-super.asciidoc | ||
btrfs-send.asciidoc | ||
btrfs-subvolume.asciidoc | ||
btrfs.asciidoc | ||
btrfsck.8 | ||
btrfstune.asciidoc | ||
CmdLineConventions | ||
CodingConventions | ||
DocConventions.asciidoc | ||
Experimental.md | ||
fsck.btrfs.asciidoc | ||
Makefile.in | ||
manpage-base.xsl | ||
manpage-bold-literal.xsl | ||
manpage-normal.xsl | ||
mkfs.btrfs.asciidoc | ||
ReleaseChecklist |