[fs-test] Fix disk usage for fs_resize_tests_data.

Instead of assuming that a given number of files will fill the disk,
look at the actual disk size.

ZX-2383 #comment fix failing tests.
Test: fs-test

Change-Id: I4c6ca4abe6762fad0451c4c8839deeb5234665bd

[fs] Update filesystem tests to use custom disk sizes.

- Allow tests to specify a minimum disk size and
custom FVM slice size.
- If running against a ramdisk, create a disk using
the requested parameters.
- If running against a real disk, verify it has at
least as much space as the ramdisk would before
executing the test.
- Update the "default disk size" to be significantly
smaller, with manual annotations for tests that require
larger disks. This will allow the fs-test suite to run
against smaller disks, but without failure.

ZX-1604 #comment In Progress

Test: Ramdisk and real disks
$ /boot/test/fs-test -f minfs
$ /boot/test/fs-test -f minfs -d /dev/class/block/000

Change-Id: If139bb947734ce411af839b100c8557ea9378a91

[fvm][zxcrypt] Refactor libraries to avoid fdio dependency

ZX-2266 #done

Test: Refactor; relying on exitant library/driver tests.

Change-Id: Ia54acac0fb8056c91b26c097a8efae22dd0c5b3a

[fs][test] Refactor code to reuse

Change-Id: I175933ae4c46f7e60bb83188e8154133f6a57f88

[fs] Fix filesystem tests for FAT

Change-Id: I226b0a23d2beface14138da59a68fe093182df5a

[fs][blobfs][fvm] Avoid using system GUIDs in tests

This failure is easiest to repro under the following conditions:

- Execute the fs tests under FVM (real disk)
- Wait for a test to partially complete, then kill the test
- Reboot the device; observe that the test partition is
mounted under "/data".

Change-Id: I24e8fecb155d35dea1c2139e91ea262b85999532

[fs] Execute fs integration tests on mount point in local namespace

This patch reduces the dependency on global "/tmp".

ZX-1722 #comment Done
ZX-1939 #comment In Progress

Change-Id: Ic0ec2e1fe52fafc0e0edb65fa2884af970d9571f

[fs-management] Make wait_for_device recursive

This CL teaches wait_for_driver_bind to wait for parent devices if they
have not yet been bound, and renames it to wait_for_device. This
simplifies usage when multiple devices are expected to bind, e.g.
rebinding a ramdisk with a zxcrypt device in an FVM partition.

This CL does NOT simplify the call sites which have unsafe path
manipulations involving strcpy and strcat. These buffer overflows will
be addressed in following CLs (see SEC-70).

ZX-2016 #comment Allows moving zxcrypt_create out of disk-pave.cpp

Change-Id: I218ad02d8969ab51bd1dcd35efe864355ba1b151

[fs] Allow filtering fs tests by individual filesystems

Change-Id: I537be0e908d81a2dd621770eb0c39988667b7317

[fvm] Provide target-side functionality for streaming sparse FVM to disk

- If a "--fvm" file is provided to the bootserver, it will be
transferred to the target device and paved onto disk. Similarly, if an
"--efi" provided to the bootserver, it will be paved onto a GPT
partition (separately from the first partition in the GPT, to avoid
dual-booting issues).
- Netsvc has been augmented so the tftp protocol can interpret
FVM and EFI files separately from netboot files, and appropriately
stream them to the FVM installer as they arrive.
- "install-disk-image" is a new application, capable of reading from
stdin (which is supplied from netsvc as a pipe) which parses the
images, and writes them to disk.

ZX-1194 #done

Change-Id: Idd6b05d7b4ff8cff81635747cc90e724f2e342d1

[fvm] Add support for atomically upgrading between VPartitions

ZX-1194 #comment In Progress

Change-Id: I3f0d6eb8cbd78c4e7d2920803483a1d0d8046a9a

[fs] Add support to FS tests for running on a real disk

The support for running on a real disk (or within a GPT
partition) was broken by the addition of FVM tests, which
cause the test disk to bind to an FVM driver, and later
remove that FVM driver.

This patch allows:
- Real block devices to be passed, where they are accessed by
topological name (so the FVM binding may be observed)
- Unbinding real block devices to send a BLOCK_RR_PART
message to the underlying block device (or partition) to
remove all the mounted FVM sub-partitions

Change-Id: I3009cfddb29b03135d397fe14820e5ef0e0da748

[utest] Make unexposed variables static

Change-Id: I016d058e7e83ea0b627ebd4a1da6e4ce97919617

[zx] Magenta -> Zircon

The Great Renaming is here!

Change-Id: I3229bdeb2a3d0e40fb4db6fec8ca7d971fbffb94

[fs] Allow tests to specify custom disk size

Commit 4d934b84cda11fd changed the allocated size
of ramdisks allocated to FS tests, shrinking it to 512 MB.
As a consequence, unrelated tests (which assumed a larger
disk was available) began failing.

Upgrade the FS test suite to allow custom disk sizes, if
requested. Otherwise, allocate a virtual 4GB disk.

MG-1100 #comment In progress

Change-Id: Ibea20db8c3f3a7c550323b457b23977b523854dc

[fs][test] FAT parent directory timestamps are invalid; don't test them

MG-1095 #done

Change-Id: Ice34169288e2428fc9c6d5276ab8b576ba2327df

[minfs] Increase max file size

Replace 1 indirect block in each inode with a "doubly indirect"
block, which points to more indirect blocks. This increases the
max file size from ~500mb to ~30gb.

Updated fsck to check doubly indirect block(s).

Change-Id: Iad40c6de69ab422061aeab5a300f44b630075320

[minfs][fs] Make MinFS automatically resize self on FVM

Change-Id: I3067e72adfa002a948ad6f9ba9c2cfb646adde90

[minfs][fs] Allow MinFS to mount itself on an FVM partition

Additionally, execute all MinFS tests twice: once for a
"normal" partition, and another for an FVM sparse partition.

Change-Id: I53bd57c9516266ebd0f05a019db1e2375a213912