linux-ext4 - Re: e2fsck exit codes

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]

Date:   Wed, 15 Feb 2017 10:44:27 -0500
From:   Theodore Ts'o <tytso@....edu>
To:     thanumalayan mad <madthanu@...il.com>
Cc:     linux-ext4@...r.kernel.org
Subject: Re: e2fsck exit codes

On Tue, Feb 14, 2017 at 11:00:51AM -0800, thanumalayan mad wrote:
> Thank you for the quick reply! (I was curious about the free-blocks
> 
> Would this be the way to proceed? I am hoping "-E journal_only" also
> takes care of clearing orphan inodes and still exits with a 0. (Note:
> The output I pasted above is derived from a file system created with
> default options, and does not switch off uninit_bg or
> lazy_itable_init.)

What are you trying to _do_ by, at the high level?

It should do what you want, but at this point I'm wondering _why_ you
want to do it, and whether or not it is something you _should_ be
doing.

						- Ted