在lvm卷上创建新的文件系统时,mkfs.xfs和mkfs.ext4命令都会在ioctl()系统调用上暂停。操作系统挂起,没有响应。 解决办法 在创建文件系统时候,加入-K的参数,在创建时禁止用块丢弃,详细的参数说明参考如下: -K Keep, do not attempt to discard blocks at mkfs time (discarding blocks initially is useful on so...
Discarding device blocks:done Creating filesystem with 31258710 4k blocks and 7815168 inodes Filesystem UUID: 6077971a-8a7c-4e41-a8bc-43ac01efedae Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424, 20480000,...
If you don't care about write performance, you do not have to care about discarding blocks either. Physical blocks will be erased when they are needed. If you need to guarantee a spcific write performance, you have to think about when to erase blocks. In general there are three options ...
Attempt to discard blocks at mkfs time (discarding blocks initially is useful on solid state devices and sparse / thin-provisioned storage). When the device advertises that discard also zeroes data (any subsequent read after the discard and before write returns zero), then mark all not-yet-ze...
Raw -K Keep, do not attempt to discard blocks at mkfs time (discarding blocks initially is useful on solid state devices and sparse / thin-provisioned storage). 1. 2. 3. Example: Raw # mkfs.ext4 -K </dev/mapper/path_to_lvm_volume> # For ext4 filesyst...
Attempt to discard blocks at mkfs time (discarding blocks initially is useful on solid state devices and sparse / thin-provisioned storage). When the device advertises that discard also zeroes data (any subsequent read after the discard and before write returns zero), then mark all not-yet-ze...
Attempt to discard blocks at mkfs time (discarding blocks initially is useful on solid state devices and sparse / thin-provisioned storage). When the device advertises that discard also zeroes data (any subsequent read after the discard and before write returns zero), then mark all not-yet-ze...
Attempt to discard blocks at mkfs time (discarding blocks initially is useful on solid state devices and sparse / thin-provisioned storage). When the device advertises that discard also zeroes data (any subsequent read after the discard and before write returns zero), then mark all not-yet-z...