Strange 2TB HDD behavior

[bmarkus]

/dev/sda1 ? Wasn't the issue with /dev/sda2?

[Rich]

Hi jgrulich

 ---- snip ----

Code: (bash) [Select]

sudo mkfs.ext4 /dev/sda1
---- snip ----
The strange LED flashing was there again, but found that in the

Code: (bash) [Select]

top
is some background root service like [ext4...]
Probably some indexing service which took some hours and now it's no more there and LED flashing disappeared.
This service is probably not run for small discs and therefor not visible.

Was the background service  ext4lazyinit  by any chance? See:
https://www.thomas-krenn.com/en/wiki/Ext4_Filesystem#Lazy_Initialization

[jgrulich]

/dev/sda1 ? Wasn't the issue with /dev/sda2?

Béla,

yes, it was sda2 before. Now I've swapped the partitions (sda2 to sda1) to have the main one as a first when used parted.
No another difference.

[jgrulich]

Hi jgrulich
Was the background service  ext4lazyinit  by any chance? See:
https://www.thomas-krenn.com/en/wiki/Ext4_Filesystem#Lazy_Initialization

Yes, you're right. That was the running service.

[Lee]

I'm -still- not a raspberry pi user and I don't have any multi-terabyte storage devices, but I have to ask:

Doesn't "lazy initialization" seem like a bad idea?

From the above referenced article:

In order to prevent lazy initialization, advanced options are offered by the mkfs.ext4 command:[20]

Code: [Select]

mkfs.ext4 -E lazy_itable_init=0,lazy_journal_init=0 /dev/mapper/fc-root
By specifying these options, the inodes and the journal will be initialized immediately during creation.