linux-ext4 - Re: Filesystem still has errors

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID:  <loom.20090211T222920-494@post.gmane.org>
Date:	Wed, 11 Feb 2009 22:34:45 +0000 (UTC)
From:	Raimund Andersen <anderse@....de>
To:	linux-ext4@...r.kernel.org
Subject:  Re: Filesystem still has errors

Eric Sandeen <sandeen <at> redhat.com> writes:

> 
> You should expect that checking a live filesystem will produce errors,
> actually.  So don't worry about that.  The filesystem is not quiesced,
> and it's not consistent.  That is to be expected, and it's why you see
> the different behavior w/ forcefsck vs. e2fsck -n on the live fs.
> 
> As for the spurious ENOSPC, I'm not certain.  Do you still get the error?

Thanks for your quick reply. No, at the moment, I don't get it. Yesterday, it
occured once and a reboot let it vanish, and I got it some days before. Also
then, a reboot let it disappear. So could it be of help if I collect any
information in the case it might reappear? What exactly should I do then?

Thank you, once again.

rgds Raimund

--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html