[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #32931] LVM write support, patch included
From: |
Vladimir Serbinenko |
Subject: |
[bug #32931] LVM write support, patch included |
Date: |
Wed, 30 Mar 2011 20:01:23 +0000 |
User-agent: |
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.18) Gecko/20110323 Iceweasel/3.5.18 (like Firefox/3.5.18) |
Update of bug #32931 (project grub):
Status: None => Wont Fix
Open/Closed: Open => Closed
_______________________________________________________
Follow-up Comment #3:
Allowing only when user specifically selects so sounds good in theory, in
practice, though, people will just force it without thinking of consequences
on their system. Also LVM would try to repair itself and so will conflict with
GRUB. If nothing else, if it stays non-official it clearly says that it can
damage the data.
> OTOH not having LVM write support is a complete desaster
There is a difference between considering something low-quality and actively
damaging it. I've tested LVM mirror only once for testing GRUB in such
conditions so I can't say anything about its quality. But even without lvm
mirror, if you have snapshots then probably some blocks are shared and writing
to them will change the data in snapshots as well.
The LVM write is a no-go unless a strategy is proposed which will avoid
corrupting data no matter what (this would need to be discussed at
address@hidden)
The consensus reached in last LVM discussion was to use embedding zone. Same
consensus was reached for other similar situations: mdraid, zfs and btrfs.
It would be desirable to ask LVM maintainers to allow us to use some space for
such things. E.g. we could use the space after the last usable block. It would
be helpful if one could tell to have at least e.g. 64K there. This would need
a small revival discussion at address@hidden None of this was done yet.
Since LVM write probably will never be accepted, marking it as wontfix. For
embedding area please discuss upstream.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?32931>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/