On Mon, Jan 08, 2024 at 07:52:33AM -0500, Brian J. Murrell wrote: > On Thu, 2024-01-04 at 09:13 -0500, Brian J. Murrell wrote: > > On Wed, 2024-01-03 at 20:55 -0800, Darrick J. Wong wrote: > > > Curious. Normally e2scrub will run e2fsck twice: Once in journal- > > > only > > > preen mode to replay the journal, then again with -fy to perform > > > the > > > full filesystem (snapshot) check. > > > > It is doing that. I suspect the first e2fsck is silent. > > > > > I wonder if you would paste the output of > > > "bash -x e2scrub /dev/rootvol_tmp/almalinux8_opt" here? I'd be > > > curious > > > to see what the command flow is. > > > > Sure. > > Was the bash -x output useful in any way, or was any of the information > I supplied in my other replies on this list: > > https://lore.kernel.org/linux-ext4/51aa3ceea05945c9f28e884bc2f43a249ef7e23e.camel@xxxxxxxxxxxxxxx/ > https://lore.kernel.org/linux-ext4/be5e8488f8484194889216603d2aba2812c6adcb.camel@xxxxxxxxxxxxxxx/ > > useful including the test of 1.47.0 being able to reproduce the > behaviour? It was good and bad -- good in that it eliminated all of my hypotheses about what could be causing it; and bad in that now I have no idea. *Something* is causing the e2fsck exit code to be nonzero, but there's nothing identifying what did that in the stdout/stderr dump. > Any thoughts on how to proceed? If you're willing to share a metadata dump of the filesystem, injecting: e2image -Q "${snap_dev}" /tmp/disk.qcow2 right before the second e2fsck invocation in check() might help us get a reproducer going. Please compress the qcow2 file before uploading it somewhere. --D > Cheers, > b. >
