** Description changed:
- To be filled in...
+ 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 problems for
** 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
** 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 Kernel
Packages, which is subscribed to linux in Ubuntu.
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
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
Awesome, thanks.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1371591
Title:
file not initialized to 0s under some conditions on VMWare
Status in “linux” package in Ubuntu:
In
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
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1371591
Title:
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
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}
==
10 matches
Mail list logo
