All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Anton Mitterer <calestyo@scientia.net>
To: fdmanana@gmail.com, Chris Murphy <lists@colorremedies.com>
Cc: Andrei Borzenkov <arvidjaar@gmail.com>,
	The development of GNU GRUB <grub-devel@gnu.org>,
	"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs trim erases bootloader area
Date: Fri, 08 Jan 2016 02:44:15 +0100	[thread overview]
Message-ID: <1452217455.6686.10.camel@scientia.net> (raw)
In-Reply-To: <CAL3q7H5Ac2OBhQvGA77=HmcgdRcV1UDPjWiyzkB7zWJF=upiHw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 468 bytes --]

Hey.

Just a followup on this:
GPT and some others (e.g MD RAID) store data in the end of the device.

It's clear that when the fs is made inside a partition, this shouldn't
be seen (and thus TRIMmed) anyway... but can btrfs be installed e.g.
directly on the device while that continues to hold the GPT (by btrfs
simply always starting at some byte offset)?
If so, then one may possibly need to extend that patch for the end of
the device.

Cheers,
Chris.

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5930 bytes --]

  parent reply	other threads:[~2016-01-08  1:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-07 19:11 btrfs trim erases bootloader area Andrei Borzenkov
2016-01-07 19:16 ` Filipe Manana
2016-01-07 22:05   ` Chris Murphy
2016-01-07 23:10     ` Filipe Manana
2016-01-07 23:39       ` Chris Murphy
2016-01-07 23:39         ` Chris Murphy
2016-01-08  1:44       ` Christoph Anton Mitterer [this message]
2016-01-08  6:36         ` Andrei Borzenkov
2016-01-07 19:19 ` Holger Hoffstätte

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1452217455.6686.10.camel@scientia.net \
    --to=calestyo@scientia.net \
    --cc=arvidjaar@gmail.com \
    --cc=fdmanana@gmail.com \
    --cc=grub-devel@gnu.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lists@colorremedies.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.