Re: Vmware ESXi5 Build 623860 - UNMAP Bit

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Apr 02, 2012 at 04:29:49PM -0700, Nicholas A. Bellinger wrote:
> On Tue, 2012-03-27 at 14:26 +0200, Stefan Gourguis wrote:
> > Dear List,
> > 
> > i have connected an new ESXi5 (Update1 Build) to an Debian 6 LIO Target (Git commit e163b66985fa162bd7c1e29a049b336bc2790a2e).
> > The Esxi Server is single FC connected to Lio (P2P)..
> > Lio-Target serves n 100 GB LVM Disk via iblock to the ESXi.
> > I started installing  an Windows 7 VM on this Datastore (VMFS 5.54)
> > 
> > "Strong as a LIO-N" gives me a lot of Errors in  dmesg: 
> > 
> > [ 1146.241497] MODE SENSE: unimplemented page/subpage: 0x1c/0x02
> > [ 1231.742035] WRITE_SAME w/o UNMAP bit not supported for Block Discard Emulation
> > [ 1231.753493] WRITE_SAME w/o UNMAP bit not supported for Block Discard Emulation
> > [ 1231.765680] WRITE_SAME w/o UNMAP bit not supported for Block Discard Emulation
> > [ 1300.303536] WRITE_SAME w/o UNMAP bit not supported for Block Discard Emulation
> > [ 1300.308241] WRITE_SAME w/o UNMAP bit not supported for Block Discard Emulation
> > [ 1300.312904] WRITE_SAME w/o UNMAP bit not supported for Block Discard Emulation
> > [ 1313.008761] WRITE_SAME w/o UNMAP bit not supported for Block Discard Emulation
> > [ 1313.013449] WRITE_SAME w/o UNMAP bit not supported for Block Discard Emulation
> > [ 1313.018111] WRITE_SAME w/o UNMAP bit not supported for Block Discard Emulation
> > [ 1316.343687] WRITE_SAME w/o UNMAP bit not supported for Block Discard Emulation
> > [ 1316.348386] WRITE_SAME w/o UNMAP bit not supported for Block Discard Emulation
> > [ 1316.353041] WRITE_SAME w/o UNMAP bit not supported for Block Discard Emulation
> > [ 1320.468975] WRITE_SAME w/o UNMAP bit not supported for Block Discard Emulation
> > [ 1320.473646] WRITE_SAME w/o UNMAP bit not supported for Block Discard Emulation
> > [ 1320.478306] WRITE_SAME w/o UNMAP bit not supported for Block Discard Emulation
> > ...
> > 
> 
> Hi Stefan,
> 
> The bugfix to make this work by default w/o the extra esxcli call to
> explicitly disable VAAI on all LUNs was reported by Martin Svec, and
> went into v3.2-rc5 here:
> 
> target: Fix unsupported WRITE_SAME sense payload
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=67236c44741e250199ccd77f1115568e68cf8848
> 
> However it appears I missed the CC to stable on this one..

Odd, I see that showing up in the 3.3-rc3 kernel, not 3.2-rc5, what am I
getting wrong?

> Greg-KH (CC'ed) would you mind including this into v3.1 and v3.0 stable
> releases for distros to pick up..?

The 3.1 kernel is now unsupported, and this patch does apply to 3.2, so
I added it there, but it does not apply to the 3.0 kernel at all, sorry.
If you want me to apply it there, please provide a backported version.
And if I shouldn't have applied it to 3.2, please let me know and I'll
remove it.

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe target-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux SCSI]     [Kernel Newbies]     [Linux SCSI Target Infrastructure]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Device Mapper]

  Powered by Linux