Re: [PATCH] debugfs: quiet debugfs 'catastrophic' message

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Aug 05, 2022 at 04:06:07PM -0600, Andreas Dilger wrote:
> When debugfs runs with "-c", it prints a scary-looking 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 for
> commands run against very large filesystems.
> 
> 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@xxxxxxxxx>
> Reviewed-by: Dongyang Li <dongyang@xxxxxxx>
> Change-Id: I59b26a601780544ab995aa4ca7ab0c2123c70118

Applied, thanks!

					- Ted



[Index of Archives]     [Reiser Filesystem Development]     [Ceph FS]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite National Park]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Device Mapper]     [Linux Media]

  Powered by Linux