Page 1 of 2 12 LastLast
Results 1 to 10 of 20

Thread: Btrfs File-System Mount Option Testing From Linux 3.14

Hybrid View

  1. #1
    Join Date
    Jan 2007
    Posts
    14,560

    Default Btrfs File-System Mount Option Testing From Linux 3.14

    Phoronix: Btrfs File-System Mount Option Testing From Linux 3.14

    Following our recent HDD benchmarking and solid-state drive testing of the Linux 3.14 kernel with various file-systems, for this weekend article we have done more tests of Btrfs on Linux 3.14 when trying out various Btrfs mount options.

    http://www.phoronix.com/vr.php?view=19940

  2. #2
    Join Date
    Mar 2010
    Posts
    24

    Default

    Off-topic, but: @Michael: why are your recent photo shots so yellow?

  3. #3
    Join Date
    Aug 2008
    Location
    Finland
    Posts
    1,578

    Default

    Wrt last test, nodatacow is pretty much eat-my-data. It turns off checksumming so Btrfs won't detect if your data gets corrupted and can lead to in time catastrophic results since there's no possibility of having on-boot fsck detect corruption either.

  4. #4
    Join Date
    Aug 2012
    Location
    Pennsylvania, United States
    Posts
    1,874

    Default

    Quote Originally Posted by nanonyme View Post
    Wrt last test, nodatacow is pretty much eat-my-data. It turns off checksumming so Btrfs won't detect if your data gets corrupted and can lead to in time catastrophic results since there's no possibility of having on-boot fsck detect corruption either.
    True, but nodatacow can be turned on/off per filesystem, subvolume, and even i think per file so its only REALLY an issue here where its off for the whole filesystem

  5. #5
    Join Date
    Jan 2009
    Posts
    1,330

    Default

    Quote Originally Posted by nanonyme View Post
    Wrt last test, nodatacow is pretty much eat-my-data. It turns off checksumming so Btrfs won't detect if your data gets corrupted and can lead to in time catastrophic results since there's no possibility of having on-boot fsck detect corruption either.
    On platters, yeah, but on ssds I don't think it would matter since the controller decides where to put the data. That is, I'm not sure it differentiates between cow and nodatacow.
    I'd be curious about how combinations of options benchmark. So, say, space cache, lzo, discard(this should only run during downtime so shouldn't affect benchmarks), ssd spread and noatime(although modification times should still register).

  6. #6
    Join Date
    Oct 2013
    Posts
    73

    Default

    In 2 years time, no one will hear anything about ZFS.

  7. #7
    Join Date
    Aug 2013
    Posts
    80

    Default

    Would BTRFS be good for USB flash drives and SD cards? What kind of CPU overhead is expected with LZO and ZLIB compression especially on a Silvermont Atom based PCs or even on older Atoms like the ones in old Compulab devices?

  8. #8
    Join Date
    Oct 2013
    Posts
    240

    Default

    Quote Originally Posted by endman View Post
    In 2 years time, no one will hear anything about ZFS.
    Thanks for giving me the laugh! Good one!

  9. #9
    Join Date
    Sep 2009
    Posts
    59

    Default Seconded

    Quote Originally Posted by liam View Post
    On platters, yeah, but on ssds I don't think it would matter since the controller decides where to put the data. That is, I'm not sure it differentiates between cow and nodatacow.
    I'd be curious about how combinations of options benchmark. So, say, space cache, lzo, discard(this should only run during downtime so shouldn't affect benchmarks), ssd spread and noatime(although modification times should still register).
    I also want to know the best combo. Please think like an admin when testing:
    1. Take corruption switches out of consideration
    2. Find the best combination.

  10. #10
    Join Date
    Mar 2014
    Posts
    1

    Default

    Does anyone know something about the state of lz4 transparent (de)compression in btrfs? I think with it's higher (de)compression speed lz4 should perform even better than lzo/zlib for transparent (de)compression in btrfs.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •