> On Fri, Jul 14, 2017 at 06:22:16PM -0700, Marc MERLIN wrote:
> > Dear Chris and other developers,
]zac[
> Others on this thread with the same error: did anyone recover from this
> without wiping the filesystem?
>
> Is there a chance a balance might work around the bug so that whatever
> layout I have, changes, and stops the bug from occuring?
]zac[
Any attempt, even just delete files, has worsened the situation.
I advise not to waste time in repairs, and directly recreate the filesystem.
My workaround is to avoid being more than one btrfs tools running.
progResult=0
while read proc; do
if [ $progResult == 0 ]; then
echo -e \nbtrfs tools already running
progResult=222
fi
echo $proc"
done < <(ps -ef | grep -e "btrfs \{1,\}\(subvolume\|send\|receive\|delete\)")
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
