public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Tso" <tytso@mit.edu>
To: Bough Chen <haibo.chen@nxp.com>
Cc: "jack@suse.cz" <jack@suse.cz>,
	"adilger.kernel@dilger.ca" <adilger.kernel@dilger.ca>,
	"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
	"imx@lists.linux.dev" <imx@lists.linux.dev>
Subject: Re: ext4 issue on  linux-next(next-20251030)
Date: Thu, 30 Oct 2025 18:33:35 -0700	[thread overview]
Message-ID: <20251031013335.GA10593@macsyma-3.local> (raw)
In-Reply-To: <DU0PR04MB9496D99F17904D1B2EFB9E5090FBA@DU0PR04MB9496.eurprd04.prod.outlook.com>

On Thu, Oct 30, 2025 at 11:11:51AM +0000, Bough Chen wrote:
> Hi Jack,
> 
> On the latest linux-next, I find your patch acf943e9768e ("ext4: fix checks for orphan inodes") trigger the following issue on our imx7d-sdb board.
> I do not have enough background knowledge of ext4, so don't know why there are orphan inodes on the partition with ext4. Not sure whether this 
> is a real issue or we need some special operation on current ext4 partition.

If you are willing to let me to see your file
names, you could send me just the metadata blocks so I can examine file
system image.  The details are in the REPORTING BUGS section of the
e2fsck man page and as well as the RAW IMAGE FILE and QCOW2 IMAGE FILE
sections of the e2image man page, but the short version is:


            e2image -Q /dev/mmcblkp2p2 fs.qcow2
            bzip2 -z fs.qcow2

... and then send me the fs.qcow2.bz file.

If you aren't please try running "dumpe2fs -h /dev/mmcblk2p2" and send
me the output.

Thanks,

						- Ted

  reply	other threads:[~2025-10-31  1:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20251023-qm_dts-v1-0-9830d6a45939@nxp.com>
     [not found] ` <20251023-qm_dts-v1-2-9830d6a45939@nxp.com>
2025-10-30 11:11   ` ext4 issue on linux-next(next-20251030) Bough Chen
2025-10-31  1:33     ` Theodore Tso [this message]
2025-10-31  2:31       ` Bough Chen
2025-11-03  3:57         ` Bough Chen
2025-11-03  8:46           ` Jan Kara

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=20251031013335.GA10593@macsyma-3.local \
    --to=tytso@mit.edu \
    --cc=adilger.kernel@dilger.ca \
    --cc=haibo.chen@nxp.com \
    --cc=imx@lists.linux.dev \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    /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