The last time I tried to do strace, I was writing output to the target
disk, which interfered with the reproduction. To remedy this, I mounted
a scratch ext4 volume to write the strace data. What it shows is a
rename() call returning ENOSPC. This looks like a btrfs bug which should
be pushed upstre
Oddly enough, it succeeds while running dpkg under strace:
root@btrfstest:/tmp# dpkg -i
/media/cdfom/pool/main/l/linux/linux-headers-3.0.0-12-server_3.0.0-12.20_amd64.deb
(Reading database ... 27834 files and directories currently installed.)
Unpacking linux-headers-3.0.0-12-server ( from
.../li
Also:
Unpacking the affected .deb file (linux-
headers-3.0.0-12_3.0.0-12.20_all.deb) into /tmp (using dpkg-deb)
succeeds.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/893681
Title:
No space left o
There are no inode limits on btrfs: df -i reports 0 total, 0 free, and 0
used.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/893681
Title:
No space left on device during kernel update on btrfs
To m
