>
>
> -Original Message-
> From: Grant Edwards
> Sent: Saturday, November 12, 2022 7:55 PM
> To: gentoo-user@lists.gentoo.org
> Subject: [gentoo-user] Re: e2fsck -c when bad blocks are in existing file?
>
> On 2022-11-12, Michael wrote:
>
> &g
On 2022-11-12, Michael wrote:
> Have your questions been answered satisfactorily by Lawrence's contribution?
Yes, Lawrence's experiment answered the my question: e2fsck adds the
bad block to the "bad block" inode and leaves it also allocated to the
existing file.
Presumably if you don't allow
On Saturday, 12 November 2022 16:44:05 GMT Grant Edwards wrote:
> On 2022-11-12, Michael wrote:
> > On Wednesday, 9 November 2022 16:53:13 GMT Laurence Perkins wrote:
> >> Badblocks doesn't ask to write anything at the end of the run. You
> >> tell it whether you want a read test, a write-read
On 2022-11-12, Michael wrote:
> On Wednesday, 9 November 2022 16:53:13 GMT Laurence Perkins wrote:
>
>> Badblocks doesn't ask to write anything at the end of the run. You
>> tell it whether you want a read test, a write-read test or a
>> read-write-read-replace test at the beginning.
>
> Not
get allocated again.
Hopefully this answers the question sufficiently.
LMP
-Original Message-
From: Grant Edwards
Sent: Wednesday, November 9, 2022 4:19 PM
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: e2fsck -c when bad blocks are in existing file?
On 2022-11-09, Wol wrote
On 2022-11-09, Wol wrote:
> On 09/11/2022 23:31, Grant Edwards wrote:
>>> If I recall correctly, it will add any unreadable blocks to its
>>> internal list of bad sectors, which it will then refuse to allocate
>>> in the future.
>
> I doubt you recall correctly.
The e2fsck man page states
On 09/11/2022 23:31, Grant Edwards wrote:
If I recall correctly, it will add any unreadable blocks to its
internal list of bad sectors, which it will then refuse to allocate
in the future.
I doubt you recall correctly. You should ONLY EVER conclude a block is
bad if you can't write to it.
On 2022-11-08, Laurence Perkins wrote:
>>>
What happens when the bad block is _already_allocated_ to a file?
>>
>>> [...]
>>
>>Thanks. I guess I should have been more specific in my question.
>>
>>What does e2fsck -c do to the filesystem structure when it discovers
>>a bad block that is
On Tue, 08 Nov 2022 12:55:51 -0500,
Laurence Perkins wrote:
>
>
>
> >-Original Message-
> >From: Grant Edwards
> >Sent: Tuesday, November 8, 2022 6:28 AM
> >To: gentoo-user@lists.gentoo.org
> >Subject: [gentoo-user] Re: e2fsck -c when bad blocks
On Tuesday, 8 November 2022 17:55:51 GMT Laurence Perkins wrote:
> >-Original Message-
> >From: Grant Edwards
> >Sent: Tuesday, November 8, 2022 6:28 AM
> >To: gentoo-user@lists.gentoo.org
> >Subject: [gentoo-user] Re: e2fsck -c when bad blocks are in exist
>-Original Message-
>From: Grant Edwards
>Sent: Tuesday, November 8, 2022 6:28 AM
>To: gentoo-user@lists.gentoo.org
>Subject: [gentoo-user] Re: e2fsck -c when bad blocks are in existing file?
>
>On 2022-11-08, Michael wrote:
>> On Tuesday, 8 November 2022
On 2022-11-08, 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
12 matches
Mail list logo
