Lines Matching full:volume

12 filesystem type, partitioning, volume management, boot options and
57 - Filesystem layout: The root filesystem is hosted in a read-only volume. The
58   /var directory is mounted in a read-write volume that persists through code
60   ssh keys, so it is a bind mount to a directory in the read-write volume. A
68         | Read-only volume | | Read-write volume           |
95   MTD partition for U-Boot, one for its environment, and a UBI volume spanning
137   logical volume to the kernel, although a [pre-init script][] will likely still
147   volume design.
167   - Volume management: LVM. This allows for dynamic partition/removal, similar
170     able to resize the partition if needed. In addition, UBI volume management
176     tree. This volume would be mounted as /boot. This allows U-Boot to load the
178     assign the remaining eMMC flash as a single physical volume containing
185     rootfs from a logical volume. An initramfs allows for flexibility if
188     volume(s). To boot the rootfs, the initramfs would search for the desired
189     rootfs volume to be mounted, instead of using the U-Boot environments.
192     separate SPI NOR modules, the logical volume in the eMMC would be mounted in
198     Therefore, have the initramfs create the LVM volume and fetch the rootfs
199     file into tmpfs from an external source to flash the volume. The rootfs file
202     build process to setup the LVM volume and create the image file.