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


Groups > linux.debian.user > #276509

Re: ext4 FS Crash

From Daniel Harris <mail.dharris@googlemail.com>
Newsgroups linux.debian.user
Subject Re: ext4 FS Crash
Date 2025-01-13 16:30 +0100
Message-ID <K4uy5-8BUx-3@gated-at.bofh.it> (permalink)
References (7 earlier) <JQIUh-ee9P-11@gated-at.bofh.it> <JQJx0-eeCN-9@gated-at.bofh.it> <JRskp-eQbE-5@gated-at.bofh.it> <JRt6N-eRX3-9@gated-at.bofh.it> <JRZq1-fH0i-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

Just an Update to this thread.

It was actually a software bug in desktop-portal (or something like that).
Once that was removed my system has been rock solid.

Thanks Dan


On Tue, Dec 10, 2024 at 3:41 AM Max Nikulin <manikulin@gmail.com> wrote:

> On 09/12/2024 00:14, Michael Stone wrote:
> > Not all drives
> > support 4k, and many that do get no benefit from such a configuration.
> [...]
> > # nvme id-ns -H /dev/nvme0n1 | grep Rel
> > LBA Format  0 : Metadata Size: 0   bytes - Data Size: 512 bytes -
> > Relative Performance: 0x2 Good (in use)
> > LBA Format  1 : Metadata Size: 0   bytes - Data Size: 4096 bytes -
> > Relative Performance: 0x1 Better
>
> It is my case. I decided that ext4 uses 4k blocks anyway, so it is
> better to be consistent with hardware&firmware developers.
>
> As to erase block size, my expectation is that some drivers might
> benefit if that size is known: flushing caches (especially in laptop
> mode), allocating space for new files. I have no evidences that it is
> implemented though. Perhaps dedicated chips and caches inside drives may
> do it more efficiently (besides dumb cheap models).
>
> mkfs.* tools might use erase block size to align filesystem structures.
>
> It is the reason why I was surprised that erase block size is not
> exposed to kernel.
>
> My real curiosity was caused by "not mounting" a drive to allow self
> healing. "Idle" is imprecise from my point of view, but I think we may
> stop here. There is a chance that I will accidentally notice a detailed
> article on this topic.
>
>
>

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