Google Git
Sign in
fuchsia / fuchsia / be0a0c3f97b29231c9207a934063b3ce9e562dd1 / . / src / storage / fvm
tree: 9f56d3e049b7aa187cef92e98b46f4d4e32738e5 [path history] [tgz]
  1. driver/
  2. host/
  3. BUILD.gn
  4. client.cc
  5. client.h
  6. client_test.cc
  7. format.cc
  8. format.h
  9. format_test.cc
  10. fvm.cc
  11. fvm.h
  12. fvm_check.cc
  13. fvm_check.h
  14. fvm_sparse.h
  15. fvm_unit_test.cmx
  16. integrity_validation_test.cc
  17. metadata.cc
  18. metadata.h
  19. metadata_buffer.cc
  20. metadata_buffer.h
  21. metadata_test.cc
  22. partition_entry_test.cc
  23. README.md
  24. slice_entry_test.cc
  25. snapshot_metadata.cc
  26. snapshot_metadata.h
  27. snapshot_metadata_format.cc
  28. snapshot_metadata_format.h
  29. snapshot_metadata_test.cc
  30. sparse_reader.cc
  31. sparse_reader.h
  32. vmo_metadata_buffer.cc
  33. vmo_metadata_buffer.h
src/storage/fvm/README.md

The Fuchsia Volume Manager exposes a set of virtual partitions that can grow or shrink. See filesystems concepts for more detail.

The toplevel fvm directory contains the shared code for dealing with the FVM format.

  • The driver runs on Fuchsia and exposes the virtual partitions to the rest of the system.

  • The host directory contains code that runs on the development machine to generate' FVM images.