http://bugzilla.kernel.org/show_bug.cgi?id=12821 ------- Comment #7 from ddi@xxxxxxxx 2009-03-05 11:25 ------- > If it's what I think it is, it's not an anomaly; (By "anomaly" I just meant that I have no clue whether "fsck died with exit status 1" means "all OK" or "something bad happened". The console message doesn't really say anything about whether fsck exit code 1 is a good, bad or neutral thing. Just sort of states the fact, heh.) > e2fsck 1.41.3 had a bug which would cause it to ... bail out with an exit(1). Got it. No, I didn't try a forced fsck (didn't know it would be different from an automated one), but I'll re-mount ro and do just that when e2image is finished! If it still breaks, I'll upgrade e2progs as suggested? -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
