From: jacob.ritorto@gmail.com (Jacob Ritorto)
Subject: [TUHS] mkfs somewhere else?
Date: Sun, 8 Feb 2015 02:03:51 -0500 [thread overview]
Message-ID: <CAHYQbfDx=8PfQ3noy=Rnjyhsrs=y=7Tzuv4eSrgTvgdNR+ZGLA@mail.gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.11.1502081733480.3148@aneurin.horsfall.org>
what about using another minor device? Is xp0d mapped elsewhere?
On Sun, Feb 8, 2015 at 1:36 AM, Dave Horsfall <dave at horsfall.org> wrote:
> On Sun, 8 Feb 2015, Jacob Ritorto wrote:
>
> > However, when I try to mkfs, I can see the heads trying to write on the
> > headcrashed part of the disk. (Nice having those plexiglass covers!)
> >
> > Is there a way to tell mkfs (or perhaps some other program) to not try
> > to write on the damaged cylinders?
>
> Modify the driver itself?
>
> I also wrote a paper on a "bad block" system, where something like inum
> "-1" contained the list of bad sectors, but never saw it through.
>
> --
> Dave Horsfall DTM (VK2KFU) "Bliss is a MacBook with a FreeBSD server."
> http://www.horsfall.org/spam.html (and check the home page whilst you're
> there)
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> https://minnie.tuhs.org/mailman/listinfo/tuhs
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20150208/e1507360/attachment.html>
next prev parent reply other threads:[~2015-02-08 7:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-08 6:22 Jacob Ritorto
2015-02-08 6:36 ` Dave Horsfall
2015-02-08 7:03 ` Jacob Ritorto [this message]
2015-02-08 7:15 ` Jacob Ritorto
2015-02-08 17:34 ` Dave Horsfall
2015-02-08 18:52 ` Jacob Ritorto
2015-02-08 20:10 Norman Wilson
2015-02-12 15:29 ` Dave Horsfall
2015-02-12 15:50 ` cowan
2015-02-12 19:18 ` random832
2015-02-08 20:12 Norman Wilson
2015-02-08 20:20 Norman Wilson
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='CAHYQbfDx=8PfQ3noy=Rnjyhsrs=y=7Tzuv4eSrgTvgdNR+ZGLA@mail.gmail.com' \
--to=jacob.ritorto@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).