Gotchas

From btrfs Wiki
(Difference between revisions)
Jump to: navigation, search
(Created page with 'This Page lists problems one might face when trying btrfs, this are not really bugs but moslty inconveniences about things not yet implemented, or yet undocumented design decisio...')
 
(Issues)
Line 5: Line 5:
 
= Issues =
 
= Issues =
  
* compress and nodatacow don't work together (2.6.30.4+newformat2)
+
* mount -o nodatacow also disables compression
: commit e3223262e519ec1150350fea485553c2b4693d2b
+
: Merge: a616b3e 013f1b1
+
  
: When one mounts a filesystem with this options, data gets not compressed.
+
* Using mkfs.btrfs -l and -n for sizes other than 4096 is not supported
  
* compression is not as effective as one would expect (2.6.30.4+newformat2)
+
* Snapshots and subvolumes cannot yet be removed (scheduled to be fixed in 2.6.32)
: The current way compression works is not optimal for small files which are still bigger than one page (4k) this is going to be fixed.
+
 
+
* using fancy mkfs.btrfs options is going to crash the kernel when the filesystem is mounted (2.6.30.4+newformat2)
+
: -l (and prolly -n) can not yet be changed and crash the kernel, no safeguards yet when mounting such a filesystem.
+

Revision as of 14:23, 5 August 2009

This Page lists problems one might face when trying btrfs, this are not really bugs but moslty inconveniences about things not yet implemented, or yet undocumented design decisions.

Please add new things below, don't forget to add a comment on which version you observed this.

Issues

  • mount -o nodatacow also disables compression
  • Using mkfs.btrfs -l and -n for sizes other than 4096 is not supported
  • Snapshots and subvolumes cannot yet be removed (scheduled to be fixed in 2.6.32)
Personal tools