On Wednesday, 9 November 2022 16:53:13 GMT Laurence Perkins wrote:
> >
> >-Original Message-
> >From: Michael
> >Sent: Wednesday, November 9, 2022 12:47 AM
> >To: gentoo-user@lists.gentoo.org
> >Subject: Re: [gentoo-user] e2fsck -c when bad blocks are
>
>-Original Message-
>From: Michael
>Sent: Wednesday, November 9, 2022 12:47 AM
>To: gentoo-user@lists.gentoo.org
>Subject: Re: [gentoo-user] e2fsck -c when bad blocks are in existing file?
>
>On Tuesday, 8 November 2022 18:24:41 GMT Wols Lists wrote:
>
&g
On Tuesday, 8 November 2022 18:24:41 GMT Wols Lists wrote:
> MODERN DRIVES SHOULD NEVER HAVE AN OS-LEVEL BADBLOCKS LIST. If they do,
> something is seriously wrong, because the drive should be hiding it from
> the OS.
If you run badblocks or e2fsck you'll find the application asks to write data
On 08/11/2022 13:20, Michael wrote:
On Tuesday, 8 November 2022 03:31:07 GMT Grant Edwards wrote:
I've got an SSD that's failing, and I'd like to know what files
contain bad blocks so that I don't attempt to copy them to the
replacement disk.
According to e2fsck(8):
-c This option
On Tuesday, 8 November 2022 03:31:07 GMT Grant Edwards wrote:
> I've got an SSD that's failing, and I'd like to know what files
> contain bad blocks so that I don't attempt to copy them to the
> replacement disk.
>
> According to e2fsck(8):
>
>-c This option causes e2fsck to use
5 matches
Mail list logo