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 
  702  vgextend mongo03-vg00 /dev/sdd
  703  lvcreate -n test -l 100%PV mongo03-vg00 /dev/sdd 
  704  mount
  705  mkfs.ext4 -E lazy_itable_init=1 -O uninit_bg /dev/mongo03-vg00/test 

Then I ran the test.  Initially it passed, twice:

/test/db.1 /test
repro in db.1
creating f0
creating f1
touching files
hexdump f0:
0000000 0000 0000 0000 0000 0000 0000 0000 0000
*
...

But then, after doing some "multitasking" (we're working on an upgrade
to MongoDB 2.6.5) and noticing that it was finished, I ran "sync" three
times and checked the f0 files again:

hexdump db.1/f0
0000000 0000 0000 0000 0000 0000 0000 0000 0000
*
0001000 cccc cccc cccc cccc cccc cccc cccc cccc
*
0007000 0000 0000 0000 0000 0000 0000 0000 0000
*
1000000
*
hexdump db.10/f0
0000000 0000 0000 0000 0000 0000 0000 0000 0000
*
1000000
*
hexdump db.2/f0
0000000 0000 0000 0000 0000 0000 0000 0000 0000
*
0001000 cccc cccc cccc cccc cccc cccc cccc cccc
*
0007000 0000 0000 0000 0000 0000 0000 0000 0000
*
1000000
*
hexdump db.3/f0
0000000 0000 0000 0000 0000 0000 0000 0000 0000
*
0001000 cccc cccc cccc cccc cccc cccc cccc cccc
*
0007000 0000 0000 0000 0000 0000 0000 0000 0000
*
1000000
*
hexdump db.4/f0
0000000 0000 0000 0000 0000 0000 0000 0000 0000
*
0001000 cccc cccc cccc cccc cccc cccc cccc cccc
*
0007000 0000 0000 0000 0000 0000 0000 0000 0000
*
1000000
*
hexdump db.5/f0
0000000 0000 0000 0000 0000 0000 0000 0000 0000
*
1000000
*
hexdump db.6/f0
0000000 0000 0000 0000 0000 0000 0000 0000 0000
*
1000000
*
hexdump db.7/f0
0000000 0000 0000 0000 0000 0000 0000 0000 0000
*
1000000
*
hexdump db.8/f0
0000000 0000 0000 0000 0000 0000 0000 0000 0000
*
1000000
*
hexdump db.9/f0
0000000 0000 0000 0000 0000 0000 0000 0000 0000
*
1000000
*

-- 
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 to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1371591/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to