All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zdenek Kabelac <zdenek.kabelac@gmail.com>
To: "Thomas Brücker" <public0x05bf@bluewin.ch>,
	"Zdenek Kabelac" <zdenek.kabelac@gmail.com>,
	dm-devel@lists.linux.dev
Subject: Re: (Re ** 6)[1]: Extending "thin_trim" (about pseudo-raid: Why!)
Date: Wed, 20 Nov 2024 11:42:20 +0100	[thread overview]
Message-ID: <91d94f48-bae4-48eb-8604-a7522f7062c8@redhat.com> (raw)
In-Reply-To: <16c198593dc27302ab90ca7fe39bb71c.squirrel@main>

Dne 20. 11. 24 v 2:28 "Thomas Brücker" napsal(a):
> Dear Mr. Kabelac,
>
> * I have had two (real!) cases which three mechanical harddisks, that have
> had defective sectors (within warranty time!), not just announced as
> defective, but really unreadable.
>
> 1st case: Two ecolocical, energy saving samsung disks, that have both got
> unreadable sectors, happyly mutually not on the same location, connected
> as raid1: All data could be read and saved.
>
> 2nd case: An usb-disk that had got unreadable sectors with a 'pseudo-raid'
> on it: All data could be read and saved.


Hi


Any device that is showing  'error' sectors (aka  smartctl shows badblocks, 
uncorrectable errors)   should be ASAP 'recovered/copied' to another new disk 
- and such faulty disk should no longer be used for anything you care about!

If you think  the disk is still 'good enough' to not be thrown to 
trash/recycle bin -  you could probably do a surface analysis - and i.e. 
allocate partitions on a drive in such a way that HUGE portion of drive before 
and after the error  is left  as not being used/allocated   (works for HDD -   
for SSD/NVMe this obviously makes no sense) -  so then HDD reading heads are 
not damaging those errori places any more - and then you can try to use it to 
store something unimportant - i.e.  3rd. backup of something....

Using faulty drive as 'daily work  disk'  with the idea you've 'saved' 
something  makes no sense - you are just preparing yourself big troubles....


> * Experimental case: Test of 'pseudo-raid' on a dvd, the dvd was scratched
> and could partially not be read: The pseudo raid could be read without any
> problem (


Just backup all your DVDs on TiB drives  while they are still readable....


>
> * I have had at least two (real) cases of harddisks with each having a
> unreadable first sector (== the partition table): The laptops could
> neither

Such drives are simply an electronic waste for recycling...


> * So, for me, it is a good idea, to protect myself from defective sectors.
>
> * 'Normal' raid(1):
>    * notebooks with two harddisks in it ...?
>    * travelling with a laptop and two usb-harddisks ...?


Seriously you should really use real  raid1 instead of these rather highly 
'questionable' data protection ideas...  (if you care about your data)

And yes - all notebooks I know  have at least  2 slots for drives - one is 
typically equipped when being sold - other one is usually empty - one just has 
to dismount laptop cover and add the drive to unused slot...


Regards

Zdenek



      reply	other threads:[~2024-11-20 10:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-20  1:28 (Re ** 6)[1]: Extending "thin_trim" (about pseudo-raid: Why!) "Thomas Brücker"
2024-11-20 10:42 ` Zdenek Kabelac [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=91d94f48-bae4-48eb-8604-a7522f7062c8@redhat.com \
    --to=zdenek.kabelac@gmail.com \
    --cc=dm-devel@lists.linux.dev \
    --cc=public0x05bf@bluewin.ch \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.