FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora Marketing

 
 
LinkBack Thread Tools
 
Old 04-15-2010, 10:46 AM
Martin Sivak
 
Default Do not reinitialize LVM when starting rescue with corrupted arrays (#579986)

Fixes traceback caused by nonexistent dialogs about reinitialization of LVM in rescue mode.

I do not want to touch possibly corrupted or misdetected arrays. So just ignoring them and letting the user to do his own recovery is a better way to handle this situation.
---
rescue.py | 8 ++++++++
1 files changed, 8 insertions(+), 0 deletions(-)

diff --git a/rescue.py b/rescue.py
index 132a56c..6d4f596 100644
--- a/rescue.py
+++ b/rescue.py
@@ -105,9 +105,17 @@ class RescueInterface:
def resetInitializeDiskQuestion(self):
self._initLabelAnswers = {}

+ def questionInitializeDisk(self, path, description, size, details=""):
+ # do not reinitialize anything when starting rescue mode
+ return False
+
def resetReinitInconsistentLVMQuestion(self):
self._inconsistentLVMAnswers = {}

+ def questionReinitInconsistentLVM(self, pv_names=None, lv_name=None, vg_name=None):
+ # do not reinitialize anything when starting rescue mode
+ return False
+
def shutdown (self):
pass

--
1.6.6.1

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
 

Thread Tools




All times are GMT. The time now is 06:50 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org