From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail02.iobjects.de ([188.40.134.68]:39486 "EHLO mail02.iobjects.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752662AbcAGT2d (ORCPT ); Thu, 7 Jan 2016 14:28:33 -0500 Subject: Re: btrfs trim erases bootloader area To: Andrei Borzenkov , The development of GNU GRUB , linux-btrfs@vger.kernel.org References: <568EB86F.7070800@gmail.com> From: =?UTF-8?Q?Holger_Hoffst=c3=a4tte?= Message-ID: <568EBA24.6030700@googlemail.com> Date: Thu, 7 Jan 2016 20:19:00 +0100 MIME-Version: 1.0 In-Reply-To: <568EB86F.7070800@gmail.com> Content-Type: text/plain; charset=utf-8 Sender: linux-btrfs-owner@vger.kernel.org List-ID: On 01/07/16 20:11, Andrei Borzenkov wrote: > As discussed on opensuse-factory list, running fstrim on btrfs erases > bootloader area, rendering system unbootable. See > > https://lists.opensuse.org/opensuse-factory/2016-01/msg00067.html > https://lists.opensuse.org/opensuse-factory/2016-01/msg00090.html > > and follow-ups that demonstrate that beginning of device gets zeroed out. > > Not sure what we can do, but from GRUB side I can only see disabling > embedding support on btrfs entirely. Since you're probably not on the btrfs list and missed it earlier today: http://www.spinics.net/lists/linux-btrfs/msg50860.html -h