Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #275341

Re: ext4 FS Crash

From Max Nikulin <manikulin@gmail.com>
Newsgroups linux.debian.user
Subject Re: ext4 FS Crash
Date 2024-12-06 17:00 +0100
Message-ID <JQIUh-ee9P-11@gated-at.bofh.it> (permalink)
References (4 earlier) <JQlXH-dWpk-1@gated-at.bofh.it> <JQo9b-dXPx-3@gated-at.bofh.it> <JQGz8-ebyf-15@gated-at.bofh.it> <JQH2a-ec1x-23@gated-at.bofh.it> <JQHbP-ecqG-5@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On 06/12/2024 21:05, Jörg-Volker Peetz wrote:
> 
> As a check if the defective sectors are all mapped out I did read all 
> sectors of the partitions:
> 
>    sudo dd if=/dev/sdaX of=/dev/null bs=8M status=progress

I am curious if "nvme device-self-test" might be more effective.

Michael, thank you for the long message. Actually I wonder what is 
"idle" that allows drive to perform self-maintenance. I expect that the 
device should not be in some deep power saving state (I am yet to 
discover available tunables that allows drive to "sleep"). Should it be 
some period of time (seconds? minutes?) completely without any IO or is 
it enough if read/write speed is below some threshold and from/to 
another chip?

As to erase block size, I am aware of it. On the other hand I am 
surprised that a drive does not allow kernel to optimize writes on a 
higher level (as uSD does):

grep '' /sys/block/*/queue/discard_granularity
...
/sys/block/mmcblk0/queue/discard_granularity:4194304
/sys/block/nvme0n1/queue/discard_granularity:4096
/sys/block/sda/queue/discard_granularity:4096  # hdd (shingled)

Earlier I heard that firmware of some (USB, SD) flash drives is 
optimized for FAT. It sounded like a magic. I was afraid that it might 
have some detrimental effect on LUKS-encrypted ext4 partition. Later I 
read that it is just some storage region with small erase block size. 
This region may be small in comparison to total capacity, but it is 
enough to fit frequently overwritten FAT structures. In this form it is 
more convincing.

I do not try to dispute that some kind of self-healing may happen, but I 
do not believe in "not mounted" state. "Idle" is not precise from my 
point of view. No (or limited) IO is reasonable, but some initialization 
might be required to ensure power saving settings.

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

ext4 FS Crash Daniel Harris <mail.dharris@googlemail.com> - 2024-12-04 13:30 +0100
  Re: ext4 FS Crash Jochen Spieker <ml@well-adjusted.de> - 2024-12-04 13:50 +0100
  Re: ext4 FS Crash Eike Lantzsch ZP5CGE / KY4PZ <zp6cge@gmx.net> - 2024-12-04 15:40 +0100
    Re: ext4 FS Crash "Andrew M.A. Cater" <amacater@einval.com> - 2024-12-04 19:20 +0100
  Re: ext4 FS Crash "Alexander V. Makartsev" <avbetev@gmail.com> - 2024-12-04 17:30 +0100
  Re: ext4 FS Crash Klaus Singvogel <deb-user-ml@singvogel.net> - 2024-12-04 17:50 +0100
    Re: ext4 FS Crash Daniel Harris <mail.dharris@googlemail.com> - 2024-12-04 18:20 +0100
      Re: ext4 FS Crash Michael Stone <mstone@debian.org> - 2024-12-05 00:50 +0100
        Re: ext4 FS Crash Daniel Harris <mail.dharris@googlemail.com> - 2024-12-05 12:00 +0100
          Re: ext4 FS Crash Michael Stone <mstone@debian.org> - 2024-12-05 13:40 +0100
            Re: ext4 FS Crash Daniel Harris <mail.dharris@googlemail.com> - 2024-12-05 16:40 +0100
      Re: ext4 FS Crash Jörg-Volker Peetz <jvpeetz@web.de> - 2024-12-05 10:30 +0100
        Re: ext4 FS Crash Max Nikulin <manikulin@gmail.com> - 2024-12-05 16:30 +0100
          Re: ext4 FS Crash Erwan David <erwan@rail.eu.org> - 2024-12-05 16:40 +0100
            Re: ext4 FS Crash Andy Smith <andy@strugglers.net> - 2024-12-05 17:10 +0100
            Re: ext4 FS Crash gene heskett <gheskett@shentel.net> - 2024-12-06 02:00 +0100
          Re: ext4 FS Crash Michael Stone <mstone@debian.org> - 2024-12-05 18:50 +0100
            Re: ext4 FS Crash Jörg-Volker Peetz <jvpeetz@web.de> - 2024-12-06 14:30 +0100
              Re: ext4 FS Crash Michael Stone <mstone@debian.org> - 2024-12-06 15:00 +0100
                Re: ext4 FS Crash Jörg-Volker Peetz <jvpeetz@web.de> - 2024-12-06 15:10 +0100
                Re: ext4 FS Crash Max Nikulin <manikulin@gmail.com> - 2024-12-06 17:00 +0100
                Re: ext4 FS Crash Michael Stone <mstone@debian.org> - 2024-12-06 17:40 +0100
                Re: ext4 FS Crash Max Nikulin <manikulin@gmail.com> - 2024-12-08 17:30 +0100
                Re: ext4 FS Crash Michael Stone <mstone@debian.org> - 2024-12-08 18:20 +0100
                Re: ext4 FS Crash Max Nikulin <manikulin@gmail.com> - 2024-12-10 04:50 +0100
                Re: ext4 FS Crash Daniel Harris <mail.dharris@googlemail.com> - 2025-01-13 16:30 +0100
    Re: ext4 FS Crash Jeffrey Walton <noloader@gmail.com> - 2024-12-04 22:00 +0100
      Re: ext4 FS Crash Klaus Singvogel <deb-user-ml@singvogel.net> - 2024-12-05 08:30 +0100
        Re: ext4 FS Crash gene heskett <gheskett@shentel.net> - 2024-12-05 11:10 +0100
          Re: ext4 FS Crash Klaus Singvogel <deb-user-ml@singvogel.net> - 2024-12-05 13:10 +0100
            Re: ext4 FS Crash gene heskett <gheskett@shentel.net> - 2024-12-05 13:40 +0100
              Re: ext4 FS Crash Michael Stone <mstone@debian.org> - 2024-12-05 14:00 +0100
              Re: ext4 FS Crash Klaus Singvogel <deb-user-ml@singvogel.net> - 2024-12-05 15:00 +0100
                Re: ext4 FS Crash gene heskett <gheskett@shentel.net> - 2024-12-05 22:30 +0100
  Re: ext4 FS Crash Jeffrey Walton <noloader@gmail.com> - 2024-12-04 18:20 +0100

csiph-web