Dear all, When accessing a VHDX disc with a f18 VM (hyperv) with kernel 3.8.8-202 x86_64 I have tons of errors like:
Add. Sense: No additional sense information hv_storvsc vmbus_0_12: cmd 0x41 scsi status 0x2 srb status 0x6
I believe it is related to WRITE_SAME don't implemented in win2012 server. It seems that this patch could make the trick:
https://patchwork.kernel.org/patch/2172871/
But how could I check if I have it in my kernel or not?
Of course, I can be completely wrong. If you have any other ideas, please share :)
Thanks for any help,
Mario
On 5/8/13 9:21 AM, Mario Ceresa wrote:
Dear all, When accessing a VHDX disc with a f18 VM (hyperv) with kernel 3.8.8-202 x86_64 I have tons of errors like:
Add. Sense: No additional sense information hv_storvsc vmbus_0_12: cmd 0x41 scsi status 0x2 srb status 0x6
I believe it is related to WRITE_SAME don't implemented in win2012 server. It seems that this patch could make the trick:
https://patchwork.kernel.org/patch/2172871/
But how could I check if I have it in my kernel or not?
It went upstream in v3.9-rc1 so if you have that or later, you have it.
-Eric
Of course, I can be completely wrong. If you have any other ideas, please share :)
Thanks for any help,
Mario
Thanks Eric, I'll upgrade to 3.9 then.
Do you know if there is an easy way to know when a kernel patch goes upstream?
Mario
On 8 May 2013 16:28, Eric Sandeen sandeen@redhat.com wrote:
On 5/8/13 9:21 AM, Mario Ceresa wrote:
Dear all, When accessing a VHDX disc with a f18 VM (hyperv) with kernel 3.8.8-202 x86_64 I have tons of errors like:
Add. Sense: No additional sense information hv_storvsc vmbus_0_12: cmd 0x41 scsi status 0x2 srb status 0x6
I believe it is related to WRITE_SAME don't implemented in win2012 server. It seems that this patch could make the trick:
https://patchwork.kernel.org/patch/2172871/
But how could I check if I have it in my kernel or not?
It went upstream in v3.9-rc1 so if you have that or later, you have it.
-Eric
Of course, I can be completely wrong. If you have any other ideas, please share :)
Thanks for any help,
Mario
On 5/8/13 9:30 AM, Mario Ceresa wrote:
Thanks Eric, I'll upgrade to 3.9 then.
Do you know if there is an easy way to know when a kernel patch goes upstream?
You can search in the git tree:
[root@host linux-2.6]# git log --pretty=oneline | grep "storvsc: avoid usage" 3e8f4f4065901c8dfc51407e1984495e1748c090 [SCSI] storvsc: avoid usage of WRITE_SAME [root@host linux-2.6]# git describe --contains 3e8f4f4065901c8dfc51407e1984495e1748c090 v3.9-rc1~21^2~7
-Eric
Mario
On 8 May 2013 16:28, Eric Sandeen sandeen@redhat.com wrote:
On 5/8/13 9:21 AM, Mario Ceresa wrote:
Dear all, When accessing a VHDX disc with a f18 VM (hyperv) with kernel 3.8.8-202 x86_64 I have tons of errors like:
Add. Sense: No additional sense information hv_storvsc vmbus_0_12: cmd 0x41 scsi status 0x2 srb status 0x6
I believe it is related to WRITE_SAME don't implemented in win2012 server. It seems that this patch could make the trick:
https://patchwork.kernel.org/patch/2172871/
But how could I check if I have it in my kernel or not?
It went upstream in v3.9-rc1 so if you have that or later, you have it.
-Eric
Of course, I can be completely wrong. If you have any other ideas, please share :)
Thanks for any help,
Mario
Cool! thanks a lot!
On 8 May 2013 16:38, Eric Sandeen sandeen@redhat.com wrote:
On 5/8/13 9:30 AM, Mario Ceresa wrote:
Thanks Eric, I'll upgrade to 3.9 then.
Do you know if there is an easy way to know when a kernel patch goes upstream?
You can search in the git tree:
[root@host linux-2.6]# git log --pretty=oneline | grep "storvsc: avoid usage" 3e8f4f4065901c8dfc51407e1984495e1748c090 [SCSI] storvsc: avoid usage of WRITE_SAME [root@host linux-2.6]# git describe --contains 3e8f4f4065901c8dfc51407e1984495e1748c090 v3.9-rc1~21^2~7
-Eric
Mario
On 8 May 2013 16:28, Eric Sandeen sandeen@redhat.com wrote:
On 5/8/13 9:21 AM, Mario Ceresa wrote:
Dear all, When accessing a VHDX disc with a f18 VM (hyperv) with kernel 3.8.8-202 x86_64 I have tons of errors like:
Add. Sense: No additional sense information hv_storvsc vmbus_0_12: cmd 0x41 scsi status 0x2 srb status 0x6
I believe it is related to WRITE_SAME don't implemented in win2012 server. It seems that this patch could make the trick:
https://patchwork.kernel.org/patch/2172871/
But how could I check if I have it in my kernel or not?
It went upstream in v3.9-rc1 so if you have that or later, you have it.
-Eric
Of course, I can be completely wrong. If you have any other ideas, please share :)
Thanks for any help,
Mario
Confirmed: kernel-3.9.1-0.rc1.201.fc18.x86_64 from koji fix this issue :)
On 8 May 2013 16:40, Mario Ceresa mrceresa@gmail.com wrote:
Cool! thanks a lot!
On 8 May 2013 16:38, Eric Sandeen sandeen@redhat.com wrote:
On 5/8/13 9:30 AM, Mario Ceresa wrote:
Thanks Eric, I'll upgrade to 3.9 then.
Do you know if there is an easy way to know when a kernel patch goes upstream?
You can search in the git tree:
[root@host linux-2.6]# git log --pretty=oneline | grep "storvsc: avoid usage" 3e8f4f4065901c8dfc51407e1984495e1748c090 [SCSI] storvsc: avoid usage of WRITE_SAME [root@host linux-2.6]# git describe --contains 3e8f4f4065901c8dfc51407e1984495e1748c090 v3.9-rc1~21^2~7
-Eric
Mario
On 8 May 2013 16:28, Eric Sandeen sandeen@redhat.com wrote:
On 5/8/13 9:21 AM, Mario Ceresa wrote:
Dear all, When accessing a VHDX disc with a f18 VM (hyperv) with kernel 3.8.8-202 x86_64 I have tons of errors like:
Add. Sense: No additional sense information hv_storvsc vmbus_0_12: cmd 0x41 scsi status 0x2 srb status 0x6
I believe it is related to WRITE_SAME don't implemented in win2012 server. It seems that this patch could make the trick:
https://patchwork.kernel.org/patch/2172871/
But how could I check if I have it in my kernel or not?
It went upstream in v3.9-rc1 so if you have that or later, you have it.
-Eric
Of course, I can be completely wrong. If you have any other ideas, please share :)
Thanks for any help,
Mario
-
Eric Sandeen -
Mario Ceresa