https://bugzilla.novell.com/show_bug.cgi?id=350540 User casualprogrammer@yahoo.com added comment https://bugzilla.novell.com/show_bug.cgi?id=350540#c1 --- Comment #1 from Casual J. Programmer 2007-12-23 03:15:01 MST --- Created an attachment (id=188619) --> (https://bugzilla.novell.com/attachment.cgi?id=188619) yast2logs -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=350540 Casual J. Programmer changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|yast2 repair repair file system not working. |yast2 repair "repair file system" not working. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=350540 User casualprogrammer@yahoo.com added comment https://bugzilla.novell.com/show_bug.cgi?id=350540#c3 Casual J. Programmer changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #188619|0 |1 is obsolete| | --- Comment #3 from Casual J. Programmer 2008-01-02 08:10:54 MST --- Created an attachment (id=189027) --> (https://bugzilla.novell.com/attachment.cgi?id=189027) yast2logs This should cover it. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=350540 User casualprogrammer@yahoo.com added comment https://bugzilla.novell.com/show_bug.cgi?id=350540#c5 Casual J. Programmer changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|casualprogrammer@yahoo.com | --- Comment #5 from Casual J. Programmer 2008-01-03 01:41:02 MST --- Actually the filesystem had some problems which were fixed in the process. I used the umount /media/WS6L-Extern1 e2fsck /dev/sdb1 commands as suggested in the info pane of yast2 repair. Not sure whether it matters that /dev/sdb1 is an external firewire drive which has no fstab entry as it is only used occasionally. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=350540 Jiří­ Suchomel changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |casualprogrammer@yahoo.com -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=350540 User jsuchome@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=350540#c8 Jiří­ Suchomel changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |casualprogrammer@yahoo.com --- Comment #8 from Jiří­ Suchomel 2008-01-03 02:32:23 MST --- Hm, so is everything fixed already? Does it still report error when you run yast2 repair? (Because yast reports "Error while iterating over blocks in inode 435272: Illegal triply indirect block found" after fsck.ext2 -n) -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=350540 User casualprogrammer@yahoo.com added comment https://bugzilla.novell.com/show_bug.cgi?id=350540#c10 --- Comment #10 from Casual J. Programmer 2008-01-03 03:07:18 MST --- Created an attachment (id=189130) --> (https://bugzilla.novell.com/attachment.cgi?id=189130) yast2logs -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=350540 User casualprogrammer@yahoo.com added comment https://bugzilla.novell.com/show_bug.cgi?id=350540#c12 --- Comment #12 from Casual J. Programmer 2008-01-03 03:43:07 MST --- OK, maybe I'm too impatient. It now ran through after 12min. Logs attached. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=350540 User jsuchome@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=350540#c14 --- Comment #14 from Jiří­ Suchomel 2008-01-03 05:15:53 MST --- According to the last y2log, it looks like the check was correct now, right? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=350540 User casualprogrammer@yahoo.com added comment https://bugzilla.novell.com/show_bug.cgi?id=350540#c15 Casual J. Programmer changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|casualprogrammer@yahoo.com | --- Comment #15 from Casual J. Programmer 2008-01-03 08:11:20 MST --- Yes the check was OK, but the the drive was marked clean to begin with and the initial problem was that the check was never carried out in the first place but rather some kind of endless loop announcing it. Not sure how to recreate the situation. As far as I recall the drive / filesystem hadn't been checked for so many days and also in fact had quite some problems which were fixed. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=350540 User mkoenig@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=350540#c17 Matthias Koenig changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|mkoenig@novell.com | --- Comment #17 from Matthias Koenig 2008-01-15 06:58:52 MST --- Yes, it should be safe to call the "repair" run after the "check" run returned 8. Mostly e2fsck returns 8, when something failed in initialisation error, but there might be cases where this is not the case. Running -p does not hurt as it operates safely, if it detects the requirement for additional corrections it will exit. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=350540 User jsuchome@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=350540#c18 Jiří­ Suchomel changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #18 from Jiří­ Suchomel 2008-01-21 02:08:23 MST --- Thanks, Matthias. Fixed in yast2-repair-2.16.4 -- 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.