You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I run FEMU as a write box, instantiate pblk, and mkfs. Dmesg warns me "corrupted read LBA".
This happens each time when pblk tries to read some data from the device.
It seems that the rqd didn't return the LBA metadata correctly.
Same configuration under qemu-nvme may not print same warnings.
Note that although dmesg warns me, the mkfs command returns successfully and I can mount the device subsequently.
When I run FEMU as a write box, instantiate pblk, and mkfs. Dmesg warns me "corrupted read LBA".
This happens each time when pblk tries to read some data from the device.
It seems that the rqd didn't return the LBA metadata correctly.
Same configuration under qemu-nvme may not print same warnings.
Thanks for reporting this.
We're aware of this bug. We're looking into this. However, this doesn't affect you to use LightNVM. It's just a warning that there is a metadata mismatch between LightNVMs' version and FEMU's. You can still use file systems on top of pblk targets and the data are still correct.
For now, we suggest to comment out the WARN() statement in function pblk_read_check()
Hi,
When I run FEMU as a write box, instantiate pblk, and mkfs. Dmesg warns me "corrupted read LBA".
This happens each time when pblk tries to read some data from the device.
It seems that the rqd didn't return the LBA metadata correctly.
Same configuration under qemu-nvme may not print same warnings.
Note that although dmesg warns me, the mkfs command returns successfully and I can mount the device subsequently.
Did I mis-reconfigured?
Guest OS :
CentOS 7
Kernel version 4.16.0
VM startup scripts:
Warning messages look like this:
The text was updated successfully, but these errors were encountered: