On Sat, 2007-01-20 at 00:56 +0100, Isidore Ducasse wrote:
> Just a lexical question: if my filesystem holds errors but e2fsck
> repairs them, does one still say that it was corrupted? Anyway I
> suppose there were errors left on it because I had to hard-reboot
> it... So I didn't think it was neither the modprobe.conf update, nor a
> modprobe that caused errors.

Yeah, it wasn't corrupted, at all, it was out-of-sync due to the hard
reboot.

-- 
Chris Gianelloni
Release Engineering Strategic Lead
Alpha/AMD64/x86 Architecture Teams
Games Developer/Council Member/Foundation Trustee
Gentoo Foundation

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to