From: Stefan Wahren <stefan.wahren@i2se.com>
To: Jan Kara <jack@suse.cz>
Cc: linux-ext4@vger.kernel.org, Ojaswin Mujoo <ojaswin@linux.ibm.com>,
Harshad Shirwadkar <harshadshirwadkar@gmail.com>,
Theodore Ts'o <tytso@mit.edu>,
Ritesh Harjani <riteshh@linux.ibm.com>,
linux-fsdevel@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Geetika.Moolchandani1@ibm.com, regressions@lists.linux.dev
Subject: Re: [Regression] ext4: changes to mb_optimize_scan cause issues on Raspberry Pi
Date: Sun, 31 Jul 2022 22:42:56 +0200 [thread overview]
Message-ID: <76a9b920-0937-7bef-db55-844f0f5f6c1b@i2se.com> (raw)
In-Reply-To: <20220728100055.efbvaudwp3ofolpi@quack3>
Hi Jan,
Am 28.07.22 um 12:00 schrieb Jan Kara:
>
> Also can get filesystem metadata image of your card like:
> e2image -r <fs-device> - | gzip >/tmp/ext4-image.gz
>
> and put it somewhere for download? The image will contain only fs metadata,
> not data so it should be relatively small and we won't have access to your
> secrets ;). With the image we'd be able to see how the free space looks
> like and whether it perhaps does not trigger some pathological behavior.
i've problems with this. If i try store uncompressed the metadata of the
second SD card partition (/dev/sdb2 = rootfs) the generated image file
is nearly big as the whole partition. In compressed state it's 25 MB. Is
this expected?
next prev parent reply other threads:[~2022-07-31 20:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 13:29 [Regression] ext4: changes to mb_optimize_scan cause issues on Raspberry Pi Stefan Wahren
2022-07-24 21:43 ` Stefan Wahren
2022-07-25 15:07 ` Ojaswin Mujoo
2022-07-25 19:09 ` Stefan Wahren
2022-07-26 6:43 ` Ojaswin Mujoo
2022-07-26 15:54 ` Stefan Wahren
2022-07-28 7:37 ` Thorsten Leemhuis
2022-07-28 10:00 ` Jan Kara
2022-07-29 5:30 ` Stefan Wahren
2022-07-31 20:42 ` Stefan Wahren [this message]
2022-08-06 15:23 ` Stefan Wahren
2022-08-14 10:07 ` Stefan Wahren
2022-08-15 10:34 ` Jan Kara
2022-08-15 11:03 ` Stefan Wahren
2022-08-06 9:50 ` Stefan Wahren
2022-08-16 9:34 ` Jan Kara
2022-08-16 11:25 ` Stefan Wahren
2022-08-16 20:45 ` Stefan Wahren
2022-08-17 5:24 ` Ojaswin Mujoo
2022-08-17 10:57 ` 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=76a9b920-0937-7bef-db55-844f0f5f6c1b@i2se.com \
--to=stefan.wahren@i2se.com \
--cc=Geetika.Moolchandani1@ibm.com \
--cc=harshadshirwadkar@gmail.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ojaswin@linux.ibm.com \
--cc=regressions@lists.linux.dev \
--cc=riteshh@linux.ibm.com \
--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