We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
shareblock(san)存储使用精简制备模式时,物理主机上是通过lvm的精简制备模式进行管理的吗? 如果是,使用lvm的精简制备模式时,如果保证多台物理主机对lv进行写时,精简制备池的数据不被损坏? 如果不是,云平台是如何使用实现shareblock的精简制备的?
The text was updated successfully, but these errors were encountered:
shareblock(san)存储使用精简制备模式时,物理主机上是通过lvm的精简制备模式进行管理的吗? 如果是,使用lvm的精简制备模式时,如果保证多台物理主机对lv进行写时,精简制备池的数据不被损坏?
不是。
如果不是,云平台是如何使用实现shareblock的精简制备的?
Qcow2 on LVM.
Sorry, something went wrong.
请问一下,如果是使用qcow2实现的,那程序中是采用了一个监控程序来动态根据qcow2的实际使用大小来给lv进行动态扩容吗?
可以参考 vdsm, 核心思想类似。
No branches or pull requests
shareblock(san)存储使用精简制备模式时,物理主机上是通过lvm的精简制备模式进行管理的吗?
如果是,使用lvm的精简制备模式时,如果保证多台物理主机对lv进行写时,精简制备池的数据不被损坏?
如果不是,云平台是如何使用实现shareblock的精简制备的?
The text was updated successfully, but these errors were encountered: