http://bugzilla.opensuse.org/show_bug.cgi?id=1046968 Bug ID: 1046968 Summary: kernel 72 btrfs random out of space (no snapshots active), rsync volume copy now fails, Yast affected Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Macintosh OS: openSUSE 42.2 Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-maintainers@forge.provo.novell.com Reporter: mario_bz@mgtech.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_5) AppleWebKit/603.2.4 (KHTML, like Gecko) Version/10.1.1 Safari/603.2.4 Build Identifier: Prior to kernel 72 I was using kernel 68 and older. For over a year I was able to do a full backup of btrfs volumes using rsync -a /.... Starting with kernel 72 (I did not use 70) rsync issues messages several times during the backup that the target is full, then continues. Important: If I reformat the btrfs target and rerun, it issues messages for different files, they are never the same! The files do not get copied, they could be small 1k or 150k files. If I format the target to ext4 it works fine, or if I go back to kernel 68 is works fine with btrfs. This is occurring on 2 different macs, and on internal targets as well as externals which are connected via firewire. I did searches and found many btrfs issues but not one like this. Keep in mind when I went back to kernel 68 that is all that change, nothing else, only the kernel files so this seems to be a kernel issue. Also, I noticed that when I attempt Yast online updates some now fail with out-of-space, then I hit retry and it works! Something really wrong with btrfs on kernels beyond 68. Reproducible: Always Steps to Reproduce: 1. Format a btrfs volume 2. rsync -a /volume with no snapshots /new volume 3. Actual Results: No space on target intermittently and with different files. Changes each attempt. Expected Results: rsync should complete normally as it did on kernel 68 and prior. -- You are receiving this mail because: You are on the CC list for the bug.