ecryptfs.extend-file-random.sh.btrfs fails with "Failed to write 32 bytes, position nnnn: No space left on device"

Bug #1098584 reported by C de-Avillez
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-kernel-tests
Fix Released
Undecided
Colin Ian King

Bug Description

This happened no Quantal LTS-HWE: of the 10 job runs, 6 failed the same way. This was not observed on this version of the tests elsewhere.

01/10 12:57:29 DEBUG|base_utils:0077| Running 'which gcc'
01/10 12:57:29 DEBUG|base_utils:0114| [stdout] /usr/bin/gcc
01/10 12:57:29 DEBUG|base_utils:0077| Running 'tests/run_one.sh -K -t extend-file-random.sh -b 1000000 -D /mnt/image -l /mnt/lower -u /mnt/upper -f btrfs'
01/10 12:57:42 ERROR|base_utils:0114| [stderr] Failed to write 32 bytes, position 324112986: No space left on device
01/10 12:57:42 DEBUG|base_utils:0114| [stdout] extend-file-random FAIL

Here is the test attributes blurb from one of the runs:

{
    "distro-release": "Ubuntu 12.04",
    "distro-release-name": "precise",
    "environ": {
        "HOME": "/home/ubuntu",
        "LANG": "en_US.UTF-8",
        "LOGNAME": "ubuntu",
        "MAIL": "/var/mail/ubuntu",
        "PATH": "/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games",
        "PWD": "/home/ubuntu",
        "SHELL": "/bin/bash",
        "SHLVL": "1",
        "SSH_CLIENT": "192.168.123.1 54143 22",
        "SSH_CONNECTION": "192.168.123.1 54143 192.168.123.132 22",
        "USER": "ubuntu",
        "_": "/bin/sh"
    },
    "kernel": "3.5.0-22.34~precise1",
    "platform": {
        "arch": {
            "bits": "64bit",
            "linkage": "ELF"
        },
        "hardware": "virtual",
        "hostname": "clean-precise-generic-amd64",
        "libc": {
            "lib": "glibc",
            "version": "2.7"
        },
        "machine": "x86_64",
        "proc": "x86_64"
    },
    "timestamp": "Thursday, 10. January 2013 17:33 UTC",
    "version": "0.0.12-1"
}

Changed in ubuntu-kernel-tests:
status: New → In Progress
assignee: nobody → Colin King (colin-king)
Revision history for this message
Colin Ian King (colin-king) wrote :

I've been running this test now for 70+ interations with this kernel and cannot reproduce this bug. Are the seek positions different for each failure, or is it consistent.

Also, can you inform me what the virtual machine configuration is (number of CPUs, memory, etc) so I can try and reproduce this.

Revision history for this message
C de-Avillez (hggdh2) wrote :

this happened on both bare-metal (4 instances) and KVM images (2 instances).

I will attach the KVM XML i use for both KVM images. The KVMs run with snapshotting on disk0, and the ecryptfs storage in disk1.

All runs can be seen in https://jenkins.qa.ubuntu.com/view/LTS%20HWE/. Look for the current runs for Quantal LTS-HWE. There is also a single failure on Quantal itself, running the test on Xen Dom0: https://jenkins.qa.ubuntu.com/view/SRU%20Kernel/job/sru_kernel-quantal-xen_amd64-amd_64-mga_g200ew/6/

Revision history for this message
C de-Avillez (hggdh2) wrote :
Revision history for this message
C de-Avillez (hggdh2) wrote :
Revision history for this message
Colin Ian King (colin-king) wrote :

After some poking around it seems that btrfs is reporting it has a lot of free space and in fact it hasn't, causing this failure. Free space calculation is tricky with btrfs, see https://btrfs.wiki.kernel.org/index.php/FAQ#Help.21_I_ran_out_of_disk_space.21

So this failure is not an eCryptfs bug, but a problem with the test on btrfs. I will see if I can get a suitable fix for the test.

Revision history for this message
Colin Ian King (colin-king) wrote :
Revision history for this message
Colin Ian King (colin-king) wrote :

This fix has been merged into ecryptfs tests, will ask for it to be picked up in the tests.

See http://bazaar.launchpad.net/~ecryptfs/ecryptfs/trunk/revision/760

Changed in ubuntu-kernel-tests:
status: In Progress → Fix Committed
Revision history for this message
Colin Ian King (colin-king) wrote :

Released in ecryptfs version 102

Changed in ubuntu-kernel-tests:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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