Am Fri, 10 Feb 2017 23:15:03 +0100 schrieb Marc Joliet <mar...@gmx.de>:
> # btrfs filesystem df /media/MARCEC_BACKUP/ > Data, single: total=851.00GiB, used=831.36GiB > System, DUP: total=64.00MiB, used=120.00KiB > Metadata, DUP: total=13.00GiB, used=10.38GiB > Metadata, single: total=1.12GiB, used=0.00B > GlobalReserve, single: total=512.00MiB, used=0.00B > > Hmm, I take it that the single metadata is a leftover from running > --repair? It's more probably a remnant of an incomplete balance operation or an older mkfs version. I'd simply rebalance metadata to fix this. I don't think that btrfs-repair would migrate missing metadata duplicates back to single profile, it would more likely trigger recreating the missing duplicates. But I'm not sure. If it is a result of the repair operation, that could be an interesting clue. Could it explain "error -17" from your logs? But that would mean the duplicates were already missing before the repair operation and triggered that problem. So the question is, why are those duplicates missing in the first place as a result of normal operation? From your logs: ---8<--- snip Feb 02 22:49:14 thetick kernel: BTRFS: device label MARCEC_BACKUP devid 1 transid 283903 /dev/sdd2 Feb 02 22:49:19 thetick kernel: EXT4-fs (sdd1): mounted filesystem with ordered data mode. Opts: (null) Feb 03 00:18:52 thetick kernel: BTRFS info (device sdd2): use zlib compression Feb 03 00:18:52 thetick kernel: BTRFS info (device sdd2): disk space caching is enabled Feb 03 00:18:52 thetick kernel: BTRFS info (device sdd2): has skinny extents Feb 03 00:20:09 thetick kernel: BTRFS info (device sdd2): The free space cache file (3967375376384) is invalid. skip it Feb 03 01:05:58 thetick kernel: ------------[ cut here ]------------ Feb 03 01:05:58 thetick kernel: WARNING: CPU: 1 PID: 26544 at fs/btrfs/extent- tree.c:2967 btrfs_run_delayed_refs+0x26c/0x290 Feb 03 01:05:58 thetick kernel: BTRFS: Transaction aborted (error -17) --->8--- snap "error -17" being "object already exists". My only theory would be this has a direct connection to you finding the single metadata profile. Like in "the kernel thinks the objects already exists when it really didn't, and as a result the object is there only once now" aka "single metadata". But I'm no dev and no expert on the internals. -- Regards, Kai Replies to list-only preferred.
pgp64OIVK8aRx.pgp
Description: Digitale Signatur von OpenPGP
