linux-ext4 - Re: metadata_csum set but no space in dir leaf for checksum

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]

Message-Id: <65D4536C-0F58-4A26-A562-B665EC6CBBB2@dilger.ca>
Date:	Sun, 14 Oct 2012 00:43:47 -0600
From:	Andreas Dilger <adilger@...ger.ca>
To:	"George Spelvin" <linux@...izon.com>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: metadata_csum set but no space in dir leaf for checksum

On 2012-10-12, at 11:05 PM, George Spelvin wrote:
> I've been getting a bunch of these messages in the syslog.
> I just ran e2fsck -D the other day as recommended, but now I'm getting
> more.
> 
> They don't look harmful, but they're annoying.
> 
> Kernel 3.6.1, 64-bit
> e2fsck 1.43-WIP (22-Sep-2012)
> Using EXT2FS Library version 1.43-WIP, 22-Sep-2012
> 
> Kernel messages:
> EXT4-fs error (device md5): ext4_dirent_csum_verify:262: inode #7282272: comm nfsd: metadata_csum set but no space in dir leaf for checksum.  Please run e2fsck -D.
> EXT4-fs error (device md5): ext4_find_entry:1217: inode #7282272: comm nfsd: checksumming directory block 0

This means there was an existing directory block that was completely full and
could not have the checksum added.  It isn't harmful, the chance of having
silent corruption in this specific block is very small.

The message itself should be quieted though, since there isn't anything to be
helped by printing it continuously.  I guess there is something missing in
e2fsck that it doesn't add a checksum to this block, however.

Cheers, Andreas





--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html