dm-0: WRITE SAME failed. Manually zeroing.

Bug #1271430 reported by Paweł Michalski
70
This bug affects 10 people
Affects Status Importance Assigned to Milestone
linux-lts-raring (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

The error message appears on console

# lsb_release -rd
Description: Ubuntu 12.04.1 LTS
Release: 12.04

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.8.0-31-generic 3.8.0-31.46~precise1
ProcVersionSignature: Ubuntu 3.8.0-31.46~precise1-generic 3.8.13.8
Uname: Linux 3.8.0-31-generic x86_64
AlsaDevices:
 total 0
 crw-rw---T 1 root audio 116, 1 sty 22 2014 seq
 crw-rw---T 1 root audio 116, 33 sty 22 2014 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
CurrentDmesg:
 [ 39.241605] type=1702 audit(1390372703.731:17): op=linkat action=denied pid=1874 comm="named" path="/var/lib/bind/eduquesty.pl.hosts" dev="dm-0" ino=322249
 [ 94.609161] pcnet32: pcnet32.c:v1.35 21.Apr.2008 <email address hidden>
 [ 97.241496] ip_tables: (C) 2000-2006 Netfilter Core Team
 [ 477.172931] dm-0: WRITE SAME failed. Manually zeroing.
Date: Wed Jan 22 08:07:24 2014
InstallationMedia: Ubuntu-Server 10.04.4 LTS "Lucid Lynx" - Release amd64 (20120214.2)
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99
MachineType: VMware, Inc. VMware Virtual Platform
MarkForUpload: True
PciMultimedia:

ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-31-generic root=/dev/mapper/hostname-system ro quiet
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-31-generic N/A
 linux-backports-modules-3.8.0-31-generic N/A
 linux-firmware 1.79.7
RfKill: Error: [Errno 2] No such file or directory
SourcePackage: linux-lts-raring
UpgradeStatus: Upgraded to precise on 2012-12-02 (415 days ago)
dmi.bios.date: 07/30/2013
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/30/2013:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.

Revision history for this message
Paweł Michalski (pm-a) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in linux-lts-raring (Ubuntu):
status: New → Confirmed
Revision history for this message
Vitaliy Okulov (vitaliy-okulov) wrote :

Same problem for me, i found thouse error messages in dmesg log just right after server boot. Server - Dell R510 H700 PERC, OS 12.04.4

Revision history for this message
Diego Walisson (diegowalisson) wrote :

Same here... The message appears right affter server boot. OS 13.10 - Kernel 3.11.0-12-generic

Revision history for this message
John Doe (wat3rfall2003) wrote :

I am also affected by this problem - on a brand new Dell R720 - H710P controller, I've installed ESXi 5.5U1 fully patched and several Ubuntu Server 14.04 LTS machines. Upon days of being put to use, all of them showed that error in the syslog - sometimes in the console as well.

Is there any patch/workaround for this? Could it affect the data on the HDDs?

Revision history for this message
roland aus köln (devzero-c) wrote :

same here - 14.04 server lts virtual machine on vsphere 5.1 - for my curiousity, i see this error only with sdb and sdc but not with sda. sdb/sdc have been added later on, but they are the same type of virtual disk like sda

Revision history for this message
Andrew Newell (scytherswings) wrote :

I have been getting this error on my console on multiple vms running 14.04.1 on ESXi 4.1U1 and also on ESXi 5.5U2. The ESXi servers point to an iSCSI target on a freenas server. VMFS3, paravirtual controller and open-vm-tools installed.

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

This isn't an error only an informational message: http://unix.stackexchange.com/a/244150/134856 .

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.