From: Pavel Machek <pavel@ucw.cz>
To: tytso@mit.edu
Cc: jack@suse.com, linux-ext4@vger.kernel.org
Subject: Re: two fsck.ext4's needed to clean filesystem
Date: Wed, 22 Jul 2015 16:21:59 +0200 [thread overview]
Message-ID: <20150722142159.GA21742@amd> (raw)
In-Reply-To: <20150722141806.GA21181@amd>
Hi!
> Is that considered ok? Should fsck restart itself or report
> 'filesystem still has errors' in this case?
It definitely should in this case:
Free inodes count wrong (22999, counted=23011).
Fix? yes
delme.fsck.damaged: ***** FILE SYSTEM WAS MODIFIED *****
delme.fsck.damaged: 2053/25064 files (0.1% non-contiguous),
97825/100000 blocks
Second check...
e2fsck 1.42.12 (29-Aug-2014)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: +18015
Fix? yes
Free blocks count wrong for group #2 (36, counted=35).
Fix? yes
Free blocks count wrong (2175, counted=2174).
Fix? yes
delme.fsck.damaged: ***** FILE SYSTEM WAS MODIFIED *****
delme.fsck.damaged: 2053/25064 files (0.2% non-contiguous),
97826/100000 blocks
Fsck lied about its success (result = 1)
pavel@amd:~/misc$ cp delme.fsck.original-damaged delme.report-2
(I can make the images public. Yes, it is artificial test.)
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2015-07-22 14:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-22 14:18 two fsck.ext4's needed to clean filesystem Pavel Machek
2015-07-22 14:21 ` Pavel Machek [this message]
2015-07-22 16:33 ` Eric Sandeen
2015-07-24 14:27 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150722142159.GA21742@amd \
--to=pavel@ucw.cz \
--cc=jack@suse.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).