Subject: Re: badsect on NetBSD 1.0
To: VaX#n8 <email@example.com>
From: Terry Moore <firstname.lastname@example.org>
Date: 05/26/1996 17:14:54
> In message <199605230337.XAA16412@mcci.com>, Terry Moore writes:
> > # mount /wd0f -- mounting the device
> > # badsect /wd0f/BAD 1919748 -- per the man page
> >I get:
> > /dev/wd0f: device busy
> If badsect is trying to open the device file while it is mounted,
> as the error message would seem to indicate, this would be prohibited
> by the 4.4BSD security model at whatever the default security level is (1).
> It's academic now, but a fix might be to run at securelevel 0.
> Yet another fix might be to recode badsect :-/
> I'm pulling this from memory (or a reasonable facsimilie thereof),
> so forgive any errors.
Well, I think I was running in single-user mode, so it should have been
securelevel 0. I think, though, that the real problem was that the
sector was part of an inode cluster -- badsect's man page hints that
it will refuse to do anything in that situation, so maybe the problem
is an erroneous error message.