https://bugzilla.novell.com/show_bug.cgi?id=265008 ------- Comment #4 from keith.buck@hp.com 2007-04-20 09:51 MST ------- 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." 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. 3. yast system_repair should know how to do this and just do it... All of these are useability issues which caused me to initially think that there was no way at all to do it (I tried to do a lot of searching before filing it as a bug). The fact that yast makes it so easy to encrypt the filesystem and so hard to repair (the GUI doesn't do it at all) is probably the most frustrating for the average user, even though fixing either 1 or 2 would have solved my problem specifically. Hope that helps you triage the bug. -- 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.