[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: btrfs trim erases bootloader area

From: Filipe Manana
Subject: Re: btrfs trim erases bootloader area
Date: Thu, 7 Jan 2016 23:10:28 +0000

On Thu, Jan 7, 2016 at 10:05 PM, Chris Murphy <address@hidden> wrote:
> On Thu, Jan 7, 2016 at 12:16 PM, Filipe Manana <address@hidden> wrote:
>> On Thu, Jan 7, 2016 at 7:11 PM, Andrei Borzenkov <address@hidden> wrote:
>>> As discussed on opensuse-factory list, running fstrim on btrfs erases
>>> bootloader area, rendering system unbootable. See
>>> 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.
>> Try this (sent to the btrfs mailing list yesterday):
>> thanks
> The description is a bit confusing by referring to MBR, which mainly
> exists only at LBA 0. In the case of extended partitions, the EBR
> (using the same MBR format) is still outside the LBA range for Btrfs
> to apply fitrim ioctl. The VBR however, would be inside that range,
> and it's that 64KiB bootloader pad Btrfs reserves that's being
> inadvertently obliterated. Correct?

Right, the title and description is confusing. I lacked the
terminology and all technical details of grub, so I just used MBR to
refer to any sector containing code used by the boot loader.
Do you like the following title/change log better?

I'll resend it later or tomorrow.


> Chris Murphy

Filipe David Manana,

"Reasonable men adapt themselves to the world.
 Unreasonable men adapt the world to themselves.
 That's why all progress depends on unreasonable men."

reply via email to

[Prev in Thread] Current Thread [Next in Thread]