From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: Richard Laager <rlaager@wiktel.com>
Cc: grub-devel@gnu.org
Subject: Re: [PATCH] Don't create grubenv on ZFS
Date: Fri, 03 Feb 2012 11:22:00 +0100 [thread overview]
Message-ID: <4F2BB548.5010106@gmail.com> (raw)
In-Reply-To: <1328263657.17279.16.camel@watermelon.coderich.net>
On 03.02.2012 11:07, Richard Laager wrote:
> On Fri, 2012-02-03 at 11:05 +0100, Vladimir 'φ-coder/phcoder' Serbinenko
> wrote:
>> On 02.02.2012 12:16, Richard Laager wrote:
>>> GRUB can't write to ZFS. Creating a grubenv file leads to a misleading
>>> "sparse file not allowed" error on boot. The attached patch for
>>> grub-install skips the creation of a grubenv file on ZFS.
>> This isn't specific to ZFS. BtrFS, squash4, all variants of cpio, tar
>> and romfs are affected by the same problem. Could you expand your patch
>> to handle those?
> I suspect that handling them by name is not the best way to do this. How
> can I tell if a filesystem doesn't support writing?
I think it's the best way. One could use grub-fstest blocklist but it
has other problems. While btrfs and zfs don't hook blocklist on purpose
(COW and, more importantly, checksums), others are just almost never
sector-aligned or are compressed.
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
next prev parent reply other threads:[~2012-02-03 10:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-02 11:16 [PATCH] Don't create grubenv on ZFS Richard Laager
2012-02-03 10:05 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-02-03 10:07 ` Richard Laager
2012-02-03 10:22 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2012-02-03 11:59 ` Richard Laager
2012-02-04 22:34 ` Jordan Uggla
2012-02-05 1:26 ` Richard Laager
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=4F2BB548.5010106@gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@gnu.org \
--cc=rlaager@wiktel.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.