From: Pavel Machek <pavel@ucw.cz>
To: kernel list <linux-kernel@vger.kernel.org>,
jack@suse.com, linux-ext4@vger.kernel.org, tytso@mit.edu,
adilger.kernel@dilger.ca
Subject: ext4 warnings: extent tree (at level 2) could be narrower.
Date: Sat, 14 Dec 2019 00:02:26 +0100 [thread overview]
Message-ID: <20191213230226.GA11066@duo.ucw.cz> (raw)
[-- Attachment #1: Type: text/plain, Size: 506 bytes --]
Hi!
Periodic fsck kicked in on x86-32 machine. I did partial update in the
meantime, and was running various kernels including -next... Now I'm
getting:
data: Inode 1840310 extent tree (at level 2) could be narrower. IGNORED.
on 5 inodes. Is it harmless, or does it mean I was running buggy
kernel in the past, or...?
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next reply other threads:[~2019-12-13 23:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-13 23:02 Pavel Machek [this message]
2019-12-13 23:37 ` ext4 warnings: extent tree (at level 2) could be narrower Darrick J. Wong
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=20191213230226.GA11066@duo.ucw.cz \
--to=pavel@ucw.cz \
--cc=adilger.kernel@dilger.ca \
--cc=jack@suse.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@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).