Google Git
Sign in
fuchsia / fuchsia / main / . / src / storage / fvm
tree: 6087818d2e4e45e2deb8e15d29d0ec3e79507f05 [path history] [tgz]
  1. driver/
  2. fidl/
  3. host/
  4. meta/
  5. src/
  6. BUILD.gn
  7. client.cc
  8. client.h
  9. client_test.cc
  10. format.cc
  11. format.h
  12. format_test.cc
  13. fvm.cc
  14. fvm.h
  15. fvm_check.cc
  16. fvm_check.h
  17. fvm_driver_integration_test.cc
  18. fvm_integration_test.cc
  19. fvm_sparse.h
  20. fvm_test_instance.cc
  21. fvm_test_instance.h
  22. golden-fvm.blk
  23. integrity_validation_test.cc
  24. metadata.cc
  25. metadata.h
  26. metadata_buffer.cc
  27. metadata_buffer.h
  28. metadata_test.cc
  29. partition_entry_test.cc
  30. README.md
  31. rebuild-golden.sh
  32. resize_integration_test.cc
  33. slice_entry_test.cc
  34. sparse_reader.cc
  35. sparse_reader.h
  36. test_support.cc
  37. test_support.h
  38. vmo_metadata_buffer.cc
  39. 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.