...

+++ b/doc/job/rootfs_disk.md @@ -0,0 +1,27 @@ +# Summary +=========

=>

rootfs_disk

Please first explain what's most relevant to end user in typical usage.

Then go on explain the internal data structure and organization.

ok, I'll refactor it later.

-------- Thanks Yu Chuan

Thanks, Fengguang

...

+`rootfs_disk` defines a list of disks, these disks will be combined into one volume group(os), +this volume group will have multiple logical volume, storing multiple rootfs, each of these +logical volume corresponds to a rootfs, such as follow:

• /dev/mapper/
• .
• ├── os-openeuler_aarch64_20.03
• ├── os-openeuler_aarch64_20.03_{timestamp}
• ├── os-openeuler_aarch64_20.03_sp1
• ├── os-openeuler_aarch64_20.03_sp1_{timestamp}
• └── ...

+Addition: +1. `/dev/mapper/os-{os}_{os_arch}_{os_version}_{timestamp}`

• • is a readonly logical volume
• • used for backup and rollback

+2. `/dev/mapper/os-{os}_{os_arch}_{os_version}`

• • is a read write logical volume
• • use for boot and run job
• • defaultly, this logical volume will be wiped before every job run

+3. every logical volume default size: 10G

+4. more info can refer os_mount.md

2.23.0