On Fri, 03.07.15 13:31, Elias Probst (m...@eliasprobst.eu) wrote: > On 07/02/2015 07:22 AM, Johannes Ernst wrote: > > Mine takes an awful long time — blocking IO on the device in the awful long > > meantime — and I’m puzzled why. Does it perhaps copy (deep? references > > only?) the entire drive? > > > > I've seen a similar issue here which was caused by a obviously corrupted > btrfs volume. > 'systemd-nspawn' and 'btrfs-transacti' consumed a full CPU core and > never stopped doing so - they were just stuck there.
> Didn't get a reply in #btrfs regarding this yet and didn't get around > yet to raise this on the btrfs ML. Yeah, please report this on the kernel bugzilla and/or the btrfs ML! Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
