https://bugzilla.novell.com/show_bug.cgi?id=265008 mmarek@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mmarek@novell.com AssignedTo|mmarek@novell.com |jsuchome@novell.com Severity|Critical |Normal ------- Comment #6 from mmarek@novell.com 2007-04-24 04:01 MST ------- (In reply to comment #4)
To crystalize the bug (thanks, that did work as well as can be expected with a corrupt filesystem), I think there are three parts:
1. The man page for xfs_repair should include text like: "If the partition is encrypted, you will need to use lo_setup first and point at the loopback device."
If you encrypt the partition, then yes, you need to decrypt it before working with the data on it. I don't see how xfs_repair is special here.
2. The error message for xfs_repair should detect (or guess) that this could be the problem when it runs into "Bad superblock", and reference a message like the above.
"Bad superblock" can have a number reasons, for instance specifying a device with different filesystem or no filesystem at all :) I'll think about what could be done about 1. and 2., reassigning to maintainer of the yast repair module for the 3rd problem. BTW I don't think this is a critical bug (the failed susped can be, but not this one). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.