http://bugzilla.opensuse.org/show_bug.cgi?id=1045598 http://bugzilla.opensuse.org/show_bug.cgi?id=1045598#c2 Andreas Stieger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |astieger@suse.com, | |virt-bugs@suse.de Component|Virtualization:Other |Kernel Resolution|--- |DUPLICATE Assignee|virt-bugs@suse.de |kernel-maintainers@forge.pr | |ovo.novell.com --- Comment #2 from Andreas Stieger --- kernel team is working on semi-random false reports on no space left on btrfs in bug 981597 *** This bug has been marked as a duplicate of bug 981597 *** -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1045598 http://bugzilla.opensuse.org/show_bug.cgi?id=1045598#c3 Jimmie Butler changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jimmiebtlr@gmail.com --- Comment #3 from Jimmie Butler --- Can't access the other bug report. If it tells you anything useful, it seems after the no space is reported for a specific file, it doesn't fail the next time docker is run for the same container getting pulled. Most obvious when your pulling a massive docker container, and each failure is a different file, and it always makes it a little further than the previous run. --- Comment #4 from Jimmie Butler --- Can't access the other bug report. If it tells you anything useful, it seems after the no space is reported for a specific file, it doesn't fail the next time docker is run for the same container getting pulled. Most obvious when your pulling a massive docker container, and each failure is a different file, and it always makes it a little further than the previous run. -- You are receiving this mail because: You are on the CC list for the bug.