The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: linux-lts-trusty (Ubuntu Precise)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
** Changed in: linux (Ubuntu Trusty)
Assignee: Chris J Arges (arges) => (unassigned)
** Changed in: linux (Ubuntu Utopic)
Assignee: Chris J Arges (arges) => (unassigned)
** Changed in: linux-lts-trusty (Ubuntu Precise)
Assignee: Chris J Arges (arges) => (unassigned)
--
You receiv
utopic has seen the end of its life and is no longer receiving any
updates. Marking the utopic task for this ticket as "Won't Fix".
** Changed in: linux (Ubuntu Utopic)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Changed in: linux (Ubuntu)
Assignee: Chris J Arges (arges) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1371591
Title:
file not initialized to 0s under some conditions
To m
** Changed in: linux (Ubuntu Utopic)
Status: In Progress => Fix Committed
** Changed in: linux-lts-trusty (Ubuntu Precise)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Trusty)
Status: In Progress => Fix Committed
--
You received this bug notification be
** CVE removed: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-3610
** CVE removed: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-3611
** CVE removed: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-3646
** CVE removed: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?nam
** Tags added: kernel-bug-exists-upstream-v3.17-rc1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1371591
Title:
file not initialized to 0s under some conditions
To manage notifications about this
* should be uninstalled when testing is over.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1371591
Title:
file not initialized to 0s under some conditions
To manage notifications about this bug go
Ok so I think the issue here is that the device in ESXi is not properly
blacklisted.
Taking the patch from:
https://lkml.org/lkml/2014/10/17/442
Blacklists multiple devices and should be the better solution than my original
patch.
I've created some test builds against 3.16 and 3.13, if those aff
** Also affects: linux (Ubuntu Utopic)
Importance: Undecided
Status: New
** Also affects: linux-lts-trusty (Ubuntu Utopic)
Importance: Undecided
Status: New
** Changed in: linux-lts-trusty (Ubuntu Utopic)
Status: New => Invalid
** Changed in: linux (Ubuntu Utopic)
This bug also exists 14.10 - kernel version 3.16.0-25.33
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1371591
Title:
file not initialized to 0s under some conditions
To manage notifications about
We are on ESXi, version 5.5, according to our hosting provider.
To run the test, I created a new, 40GB virtual disk. It's attached as
SCSI ID 1:3, on a VMware Paravirtual SCSI adapter. I set it up as a PV
and put ext4 on it the "fast way," which is what I always do:
701 pvcreate /dev/sdd
@greg,
Hi which VMware platform are you on, ESX or Fusion/WS?
Could you try running the test case as described in the description to see if
it is the same issue?
Thanks,
--chris
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
Hi,
We just hit this bug on 3.13.0-39.66~precise1, running MongoDB 2.6.3.
We're running Precise, with the trusty HWE enabled. We're on VMware,
though from reading this bug report it doesn't matter.
Is there anything we can report to be helpful?
--
You received this bug notification because you
This bug was fixed in the package linux-lts-trusty -
3.13.0-39.66~precise1
---
linux-lts-trusty (3.13.0-39.66~precise1) precise; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1386866
[ Upstream Kernel Changes ]
* KVM: x86: Check non-canonical addresses up
This bug was fixed in the package linux - 3.13.0-39.66
---
linux (3.13.0-39.66) trusty; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1386629
[ Upstream Kernel Changes ]
* KVM: x86: Check non-canonical addresses upon WRMSR
- LP: #1384539
- CVE-201
Verified in my trusty VM.
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
+ SRU Justification:
+
+ [Impact]
+
Under some conditions, after fallocate() the file is observed not to be
completely initilized to 0s: some 4KB pages have left-over data from
previous files that occupied those pages. Note that in addition to
causing functional p
Fix is in Christoph Hellwig's tree, on path to 3.18 and backport to
stable. https://lkml.org/lkml/2014/9/25/482
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-lts-trusty (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1371591
Ti
** Summary changed:
- file not initialized to 0s under some conditions on VMWare
+ file not initialized to 0s under some conditions
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1371591
Title:
file
** Also affects: linux (Ubuntu Precise)
Importance: Undecided
Status: New
** No longer affects: linux (Ubuntu Precise)
** Also affects: linux-lts-trusty (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Precise)
Importance: Undecided
Status:
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from t
** Branch linked: lp:ubuntu/trusty-proposed/linux-keystone
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1371591
Title:
file not initialized to 0s under some conditions on VMWare
To manage notifica
I've nominated Precise as well based on the description indicating a
recreate there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1371591
Title:
file not initialized to 0s under some conditions on
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1371591
Title:
file not initialized to 0s under some conditions on VMWare
To manage notifications about this bug go to:
https://bu
@petr-vmware, arvindkumar:
Thanks for looking into this!
I think your analysis makes more sense, because we'd expect the manually
zeroing to actually work instead of causing corruption. What kind of testing
and configurations have you done this on?
Can you submit this patch upstream and referen
Hi Chris,
can you revert original patch which blacklist VMware for no good reason, and
instead apply attached patch, or its equivalent? As explained above, bug
affects ALL disks that do not support WRITE_SAME when used with stackable block
devices, like LVM. Due to the bug Linux kernel stops
Hi Chris,
This is Arvind Kumar from VMware. Recently the issue discussed in this
bug was brought into VMware's notice. We looked at the patch
(https://lkml.org/lkml/2014/9/23/509) which was done to address the
issue. Since the patch is done in mptsas driver, it addresses the issue
only on lsilogic
** Branch linked: lp:ubuntu/precise-proposed/linux-lts-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1371591
Title:
file not initialized to 0s under some conditions on VMWare
To manage notif
This bug was fixed in the package linux - 3.16.0-20.27
---
linux (3.16.0-20.27) utopic; urgency=low
[ Tim Gardner ]
* [Config] CONFIG_CXL=m
* Release Tracking Bug
- LP: #1376354
[ Andi Kleen ]
* SAUCE: perf tools: Fix perf record as non root with kptr_restrict == 1
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Trusty)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1371591
Patch here:
http://git.infradead.org/users/hch/scsi-queue.git/commit/4089b71cc820a426d601283c92fcd4ffeb5139c2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1371591
Title:
file not initialized to 0s
This is what the customer reports. Ignoring the CD-ROM, this is slightly
different from what I see on my VMWare Fusion installation, which reports
"VMware, " (with a comma and a space). Presumably this is an insignificant
difference?
Bruce
tail /sys/class/scsi_device/*/device/{vendor,model}
==> /s
Bruce,
The following should get some of the info needed:
tail /sys/class/scsi_device/*/device/{vendor,model}
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1371591
Title:
file not initialized to 0s
Thanks Chris.
I take it from the other thread that bubbling the setting up from the lower
layer to the dm-* layer won't be possible.
Do you know if this patch will fix it for ESXi as well as for the VMWare
desktop products? I don't have access to ESXi, but the issue was originally
reported to us
https://lkml.org/lkml/2014/9/23/509
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1371591
Title:
file not initialized to 0s under some conditions on VMWare
To manage notifications about this bug go
I can confirm that this fixes the issue, both for the mongod repro and
for the standalone repro attached to this report.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1371591
Title:
file not initial
Can you try this build and see if it fixes the issue? Please install it into
the guest VM:
http://people.canonical.com/~arges/lp1371591/
Thanks,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1371591
Ok my experiment doing the following (and I know launchpad will mangle
my spacing...):
diff --git a/block/blk-lib.c b/block/blk-lib.c
index 9b5b561..03ad981 100644
--- a/block/blk-lib.c
+++ b/block/blk-lib.c
@@ -283,6 +283,7 @@ int __blkdev_issue_zeroout(struct block_device *bdev,
sector_t sector
As a workaround, you can use IDE/SATA disks instead of SCSI (default),
I'm not sure of performance implications, but the test cases passes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1371591
Title:
As you mentioned in #10, blkdev_issue_zeroout (the function that prints
'WRITE SAME failed. Manually zeroing.'), still causes the test to show
failures even if we should be manually zeroing out the block device when
the hardware write_same fails. A test I could try is to short circuit
BLKZEROOUT t
The bisect resulted in the following:
dc019b21fb92d620a3b52ccecc135ac968a7c7ec is the first bad commit
commit dc019b21fb92d620a3b52ccecc135ac968a7c7ec
Author: Mike Snitzer
Date: Fri May 10 14:37:16 2013 +0100
dm table: fix write same support
If device_not_write_same_capable() retu
FWIW, I also tested this on a similar KVM instance using a SCSI disk
device and installed Ubuntu using LVM, running the same test case does
not result in the failure; even though write_same is enabled for those
devices.
ubuntu@lp1371591:~$ lsblk
NAMEMAJ:MIN RM SIZE RO
The bisect resulted in the following:
dc019b21fb92d620a3b52ccecc135ac968a7c7ec is the first bad commit
commit dc019b21fb92d620a3b52ccecc135ac968a7c7ec
Author: Mike Snitzer
Date: Fri May 10 14:37:16 2013 +0100
dm table: fix write same support
If device_not_write_same_capable() retu
The 'regression' is between 3.9 and 3.10-rc1. I'll bisect between these
tags to see where the issue is.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1371591
Title:
file not initialized to 0s under
@bruce-lucas
OK I have reproduced this with the latest 3.17-rc kernel. So most likely this
is an upstream issue.
However I'll start testing previous versions to see if this is a regression
between 3.10,3.11; this will help us zero in on the code changes that may have
introduced this behavior.
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1371591
Title:
file not initialized to 0s under some conditions on VMWare
To manage notifications about this bug go to:
ht
By the way, a couple more pieces of information that may be relevant:
The problem is sensitive to the particular pattern of access to map0. If
you remove either of the two writes (at 0x0 and 0x7000) the problem
disappears, or if you change 0x7000 to a higher page it also disappears.
We also obser
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1371591
Title:
file not initialized to 0s under some conditions on VMWare
To manage notifica
Awesome, thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1371591
Title:
file not initialized to 0s under some conditions on VMWare
To manage notifications about this bug go to:
https://bugs.l
I accepted all the default settings when creating the VM (which for
Fusion was 20 GB disk, 1 GB memory, single processor).
On Fusion at least It is important to do the manual install: select
installation method / more options / create a custom VM, mount the CD,
set as boot device, bot up, go thro
@bruce-lucas:
Ok! I can reproduce this issue in VMWare Workstation. I'll start investigating
more deeply.
In my KVM instance previously I did not reproduce the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1371591
Title:
file not initialized to 0s under some conditions on VMWare
To man
When creating the VM, did you use the default settings, or was the
hardware configuration changed at all? I.e. did you add extra
processors, or just use 1?
I'll look into my errors a bit more, getting VMWare Workstation setup;
has this been only reproduced in VMWare Fusion? Also are there specific
** Attachment added: "sample repro script output"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1371591/+attachment/4208971/+files/repro.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/137
20 GB should be more than enough. It should run the repro binary several
times, using more disk space each time since it leaves the each run in
place when it goes on to the next, and then get a failure from fallocate
on the last one when the disk is filled up. I've attached a file showing
a success
So are you sure 20GB is enough disk space for the VM? I tried in a KVM
VM (just to try the reproducer) and I get 'No space left on device'
errors from fallocate.
In addition can you post the machine information someone in this bug so
I can reproduce the exact setup on my end with vmware.
Also to
** Summary changed:
- FS Corruption with Ubuntu and VMWare
+ file not initialized to 0s under some conditions on VMWare
** Attachment added: "reproducer"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1371591/+attachment/4208902/+files/repro.tgz
--
You received this bug notification b
59 matches
Mail list logo
