Hello, Don. You wrote 1 марта 2013 г., 9:11:32: DL> The fact that the filesystem code called panic() indicates that the DL> filesystem was already corrupt by that point. That's a likely reason DL> for fsck complaining about the unexpected SU+J inconsistency.
DL> Incorrect write ordering that allowed the filesystem to become DL> inconsistent because some pending writes were lost because of the panic DL> might not be necessary, but this might have allowed an earlier crash DL> where a full fsck was skipped to leave the filesystem in this state. As far, as I understand, if this theory is right (file system corruption which left unnoticed by "standard" fsck), it is bug in FFS SU+J too, as it should not be corrupted by reordered writes (if writes is properly reported as completed even if they were reordered). DL> This panic might also be a result of the bug fixed in 246877, but I have DL> my doubts about that. It was not MFCed :( -- // Black Lion AKA Lev Serebryakov <l...@freebsd.org> _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
