diff options
| author | Ferenc Wagner <wferi@niif.hu> | 2010-05-31 18:40:24 +0200 |
|---|---|---|
| committer | H. Peter Anvin <hpa@linux.intel.com> | 2010-06-07 14:54:45 -0700 |
| commit | cd508a8c968deda3b91a6c46ba1a1572753f3951 (patch) | |
| tree | 5b50cf78028af923b7c94c9cc6211d30b1189b2e | |
| parent | 7f0b9b9404ba90009b656c80fb5caa444b47be9d (diff) | |
| download | syslinux-cd508a8c968deda3b91a6c46ba1a1572753f3951.tar.gz | |
menu docs: document MENU SAVE caveat with RAID-1
The usual RAID-1 ADV constraint...
Signed-off-by: Ferenc Wagner <wferi@niif.hu>
Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
| -rw-r--r-- | doc/menu.txt | 7 |
1 files changed, 6 insertions, 1 deletions
diff --git a/doc/menu.txt b/doc/menu.txt index c912c1df..af93558e 100644 --- a/doc/menu.txt +++ b/doc/menu.txt @@ -309,7 +309,12 @@ MENU NOSAVE On the other hand, it handles changes in the configuration file gracefully. - The MENU SAVE information can be cleared with + NOTE: In software RAID-1 setups MENU SAVE only stores the + default label on the actual boot disk. This may lead to + inconsistent reads from the array, or unexpectedly change the + default label after array resynchronization or disk failure. + + The MENU SAVE information can be fully cleared with "extlinux --reset-adv <bootdir>". A MENU SAVE or MENU NOSAVE at the top of a (sub)menu affects |