Whamcloud - gitweb
LU-16067 debugfs: quiet debugfs 'catastrophic' message 09/48109/4
authorAndreas Dilger <adilger@whamcloud.com>
Tue, 2 Aug 2022 21:39:12 +0000 (15:39 -0600)
committerLi Dongyang <dongyangli@ddn.com>
Fri, 5 Aug 2022 05:41:37 +0000 (05:41 +0000)
commit50300b882685154d0d79df8c3c80bd12d9c5bf86
treec4043792cb36c1acf10d93028eaf9546907698f5
parent1e3001a9e276b4a074f3061de0b7fa1cf7950ed3
LU-16067 debugfs: quiet debugfs 'catastrophic' message

When debugfs runs with the "-c" option, it prints a scary message:

    catastrophic mode - not reading inode or group bitmaps

that is often misunderstood by users to mean that there is something
wrong with the filesystem, when there is no problem at all.

Not reading the bitmaps is totally normal and expected behavior for
the "-c" option, which is used to significantly shorten the debugfs
command execution time by not reading metadata that isn't needed.

Since there is often confusion about what this message means, it
would be better to just avoid printing anything at all, since the
use of "-c" is expressly requesting this behavior, and there are
no messages printed out for other options.

Signed-off-by: Andreas Dilger <adilger@whamcloud.com>
Change-Id: I59b26a601780544ab995aa4ca7ab0c2123c70118
Reviewed-on: https://review.whamcloud.com/48109
Tested-by: jenkins <devops@whamcloud.com>
Tested-by: Maloo <maloo@whamcloud.com>
Reviewed-by: Artem Blagodarenko <ablagodarenko@ddn.com>
Reviewed-by: Li Dongyang <dongyangli@ddn.com>
debugfs/debugfs.c