Hi,
Andy Smith wrote:
> your reply doesn't make it clear to me whether the
> lazy init was the cause of your writes or not.
It seems so.
The disk is mounted without i/o being counted in /sys/block/sda/sda2/stat .
If only half of the 733702 write ops of mkfs.ext4 were due to lazy_*=0,
then they
On Tue, Sep 29, 2020 at 01:02:35PM +0200, Thomas Schmitt wrote:
> Andy Smith wrote:
> > Create with:
> >mkfs.ext4 -E lazy_itable_init=0,lazy_journal_init=0
>
> This lasts significantly longer than my first mkfs run.
> The drive makes ~ 1950 write operations per second. So i estimate that
> the
Hi,
Andy Smith wrote:
> Could it possibly be the lazy init feature of ext4, which is enabled
> by default and can sometimes result in several minutes of background
> writes to a newly-created fs?
Well, the blinking went on for at least an hour.
> Create with:
>mkfs.ext4 -E lazy_itable_init=
Hello,
On Tue, Sep 29, 2020 at 10:24:44AM +0200, Thomas Schmitt wrote:
> i have encrypted my HDD's (*) data partition. Now the disk access LED is
> blinking rapidly as soon as i mount it.
Could it possibly be the lazy init feature of ext4, which is enabled
by default and can sometimes result in s
Hi,
i have encrypted my HDD's (*) data partition. Now the disk access LED is
blinking rapidly as soon as i mount it.
Is this normal ?
I did:
cryptsetup -v -y luksFormat --type luks2 /dev/sda2
cryptsetup open /dev/sda2 daten
dd if=/dev/zero bs=512 count=7679784591 status=progress of=/dev/m
5 matches
Mail list logo