We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
We'd like to figure out what's causing this bug for you, but we haven't
heard back from you in a while. Could you please provide the requested
information? Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
IOW, most likely no bug.
--
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 manage notifications about this bug go to:
https://bugs
My guess is that the btrfs ran out of metadata space and rebalancing was
in order.
--
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
Ubuntu has not shipped a btrfs package for a long time, moving to
generic Ubuntu for triage.
This bug is pretty old. Did anyone affected by this experience it with
trusty or later?
** Package changed: btrfs (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: Confirmed => Incomplete
** Chan
I experienced this problem as well with kernal update on btrfs. Some
searching found a FAQ entry on the "no space left on device" error and
some possible workarounds:
https://btrfs.wiki.kernel.org/index.php/Problem_FAQ
I tried running the partial balance:
> sudo btrfs fi balance start -dusage=5
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
I forgot to specify that I don't have btrfs, indeed; in my case it was
an ext4 partition.
--
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
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
I had the same problem, too; in my case, I had enough free space, but I
was out of inodes. You can check if it is the case for you with this
command:
df -i
If the percentage of used inodes is near 100%, you can probably solve by
deleting something (folders with tons of small files are your enemy)
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: btrfs (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/893681
Title:
No sp
** Package changed: ubuntu => btrfs (Ubuntu)
--
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 manage notifications about this bug
14 matches
Mail list logo
