On 02/15/2016 04:43 PM, Josh Grosse wrote:
On 2016-02-15 09:08, lilit-aibolit wrote:
On 02/15/2016 04:03 PM, Josh Grosse wrote:
See the words "NO WRITE" in that message? This happens because you
are attempting to fsck(8) a *mounted* file system.
Yes, it's true. But I can't unmount /var under normal boot.
And then why errors haven't been fixed or even detected in single mode,
where partitions are unmounted.
When you are in a normal multi-user boot, daemons are running with
files open in /var,
and in particular, /var/run. The warnings you get from fsck() relate
to all of these
open files.
Your filesystem was repaired, and is now working properly. You are
only seeing these
messages because you are running fsck() against a mounted filesystem
with open files.
Thank you. This is definitely the case then.
I didn't know that fsck could produce fake errors while running on
mounted fs.
