mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Noah White <nwhite@silverbacktech.com>
To: linux-kernel@vger.kernel.org
Subject: badblocks, sector/bit copies and other musings
Date: Mon, 8 Apr 2002 09:19:53 -0400	[thread overview]
Message-ID: <E7D41DF26971D51197F100B0D020EFF856076C@kashmir.silverbacktech.com> (raw)


Greetings,

I had some general questions regarding how the kernel/fs handle bad blocks
and such and how that relates to various copying techniques such as Norton
Ghost, hardware disk duplicators (the old octopus's) and such.

Specifically, I'm curious as to how the following situation is handled. If I
have:

drive A which is say a 30 GB IDE drive which I've built in a standard
fashion with the 2.2.12-20 kernel and created two ext-2 partitions and one
swap partition

drive b which is also the same model 30 GB IDE drive which is empty and has
no file system on it OR has a windows file system (FAT or NTFS) 

Now in the case of copying drive A onto drive B using a sector or bit copy
technique and I:

1) Use Ghost with sector copy mode OR
2) Use a hardware harness which does a straight bit copy of the drive (and
is non-file system aware)

How will the bad blocks be mapped? From the file system perspective will
drive B think its bad blocks are the same as drive A thus setting drive B up
for possible errors because its bad block mappings are incorrect?

This leads to my ultimate question which is what is the safest and fastest
way to dup a linux/ext-2 drive? 

Thanks in advance,

-Noah


             reply	other threads:[~2002-04-08 13:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-08 13:19 Noah White [this message]
2002-04-09  8:41 ` Helge Hafting
2002-04-16 16:09   ` Hans-Peter Jansen

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=E7D41DF26971D51197F100B0D020EFF856076C@kashmir.silverbacktech.com \
    --to=nwhite@silverbacktech.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®