From: ValdikSS <iam@valdikss.org.ru>
To: Theodore Ts'o <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org
Subject: Re: ext4lazyinit reads HDD data on mount since 5.13
Date: Mon, 9 Aug 2021 22:34:37 +0300 [thread overview]
Message-ID: <80f2ab1e-affb-5f31-e367-3f92b61d8ad9@valdikss.org.ru> (raw)
In-Reply-To: <YRFzWGkBOHcugxGD@mit.edu>
On 09.08.2021 21:26, Theodore Ts'o wrote:
>
> It's not been tested, but it should be safe in terms that it shouldn't
> lead to any file system corruption or data loss. However, it may
> result in non-optional block placement that might cause more file or
> free-space fragmentation that might otherwise be the case. (This was
> true even before the latest optimizations, but it's more the case with
> the new optimizations.)
>
> Can you say something about why you want to disable to block
> allocation prefetch? How is it causing problems for you?
My old HDDs are now screeching their heads for 20 seconds after mount.
That's secondary disks (internal and external drives) which are not
fragmented, mostly idle and have plenty of free space. It's a bit
annoying to hear the sounds and see strange load right after mounting,
so I'd prefer old behavior.
Just aesthetics, not a technical issue per se.
next prev parent reply other threads:[~2021-08-09 19:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-08 22:13 ext4lazyinit reads HDD data on mount since 5.13 ValdikSS
2021-08-09 1:51 ` Theodore Ts'o
2021-08-09 7:43 ` ValdikSS
2021-08-09 16:18 ` harshad shirwadkar
2021-08-09 18:26 ` Theodore Ts'o
2021-08-09 19:34 ` ValdikSS [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-08-08 22:51 ValdikSS
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=80f2ab1e-affb-5f31-e367-3f92b61d8ad9@valdikss.org.ru \
--to=iam@valdikss.org.ru \
--cc=linux-ext4@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