From: "\"Thomas Brücker\"" <public0x05bf@bluewin.ch>
To: "Zdenek Kabelac" <zdenek.kabelac@gmail.com>, dm-devel@lists.linux.dev
Subject: (Re ** 6)[1]: Extending "thin_trim" (about pseudo-raid: Why!)
Date: Wed, 20 Nov 2024 02:28:39 +0100 [thread overview]
Message-ID: <16c198593dc27302ab90ca7fe39bb71c.squirrel@main> (raw)
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.
* 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 (
* ok. if the metadata on the dvd, which is responsible to have access to
the dvd at all, is scratched, you loose everything.
* about a read-only!-dvd with 'raid' on it ...: I use another 'strange'
construct with dm-target dm-snapshot to protect the dvd from writing to.
).
* I have had at least two (real) cases of harddisks with each having a
unreadable first sector (== the partition table): The laptops could
neither
been started, nor could the data.been accessed, After rewriting the
partition table, the disks worked just long enough, to copy a complete
image of them.
(either the disk has a partiton at the 'usual' location, or you may search
for the begin of the filesystem...)
* Link (I don't want to attach and clutter your mail server with unneces-
sary images) to: Defective disk in harddisk device.
"http://www.thomas-r-bruecker.ch/favorites/io/disk/Defective_disk.jpg".
(It begins mostly with defective sectors and ends in a crash.)
* 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 ...?
Sincerely
Thomas
============================================================================
On Tue, November 19, 2024 2:37 pm, Zdenek Kabelac wrote:
> Dne 19. 11. 24 v 3:11 "Thomas Bruecker" napsal(a):
>> ]...]
> [...]
> And while I can 'see' a small value in having the same data stored
> multiple times on the same drive - the protection you get from this is
> close to nothing
> [...]
> With prices of storage these days I'd simply recommend to simply use the
> raid the way it's supposed to be used.
> [...]
next reply other threads:[~2024-11-20 1:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-20 1:28 "Thomas Brücker" [this message]
2024-11-20 10:42 ` (Re ** 6)[1]: Extending "thin_trim" (about pseudo-raid: Why!) Zdenek Kabelac
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=16c198593dc27302ab90ca7fe39bb71c.squirrel@main \
--to=public0x05bf@bluewin.ch \
--cc=dm-devel@lists.linux.dev \
--cc=zdenek.kabelac@gmail.com \
/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.