>Submitter-Id: current-users
>Originator:Vladimir B. Grebenschikov
>Organization: SWsoft
>Confidential: no
>Synopsis: GEOM-related problem sysutils/diskcheckd does not work
>Severity: non-critical
>Priority: low
>Category: ports
>Cla
I did not create diskcheckd, I just ported it from src/ let me cc
some people that may know something more about it.
> Since then it was running fine for a few months. Then I did an Upgrade
> of Diskcheckd and FreeBSD on one of the machines. After that, Diskcheckd
> refused to che
What are the current plans for diskcheckd in src? I have it ported in
sysutils/diskcheckd with minor testing needed.
--
David W. Chapman Jr.
[EMAIL PROTECTED] Raintree Network Services, Inc.
[EMAIL PROTECTED] FreeBSD Committer
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
After the repo copy of the diskcheckd.conf gets done this patch
should be the last one I need to make ports/sysutils/diskcheckd to
work properly. Any comments/problems would be appreciated. I would
especially appreciate some patches to pkg-descr for a more detailed
description if possible
I'm almost finished with the port for diskcheckd. I'm just waiting
on a repo copy of the config file I forgot to include in my repo
request. When it is time to change it over from src to ports in
modules, I'd appreciate some help since I haven't made any src
com
since it keeps waking your
>> disks up).
>>
>I have the shar of the port up at
>http://people.freebsd.org:~/dwcjr/diskcheckd.shar I believe. its
>already in the ports, I'm just awaiting a repo copy of the files from
>/usr/src/usr.sbin/diskcheckd into ports/sysutils/
From: Mike Smith <[EMAIL PROTECTED]>
Subject: Re: diskcheckd is poo
Date: Fri, Aug 24, 2001 at 04:14:24PM -0700
> If we want a surface scrubber, we ought to have a "real" one; it's
> also very, very bad in the laptop context (since it keeps waking your
> disks up).
midas" <[EMAIL PROTECTED]>
To: "Mike Smith" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Saturday, August 25, 2001 2:49 AM
Subject: Re: diskcheckd is poo
> From: Mike Smith <[EMAIL PROTECTED]>
> Subject: Re: diskcheckd is poo
> Date: Fri, Aug 24
p://people.freebsd.org:~/dwcjr/diskcheckd.shar I believe. its
already in the ports, I'm just awaiting a repo copy of the files from
/usr/src/usr.sbin/diskcheckd into ports/sysutils/diskcheckd/files
--
David W. Chapman Jr.
[EMAIL PROTECTED] Raintree Network Services, Inc.
[EMAIL PROTECTED]
If we want a surface scrubber, we ought to have a "real" one; it's
also very, very bad in the laptop context (since it keeps waking your
disks up).
If we're going to keep it, it should be turned off by default at any rate.
> diskcheckd is very annoying. Many doubt its
On Thu, Aug 23, 2001 at 05:51:41PM -0500, David W. Chapman Jr. wrote:
> Here is a shar of what I am working on. Comments patches and
> complaints are appreciated. I just have to make the rc script for it
> to startup on boot.
>
> http://people.freebsd.org/~dwcjr/diskcheckd.shar
> --
Update
On Thu, Aug 23, 2001 at 01:57:15PM -0700, David O'Brien wrote:
> On Thu, Aug 23, 2001 at 03:11:00PM -0500, David W. Chapman Jr. wrote:
> > If someone could roll a tarball for me, I could atleast make the
> > skeleton for the port if not finish it off.
>
> We should just repo copy it to ports. S
On Thu, Aug 23, 2001 at 03:11:00PM -0500, David W. Chapman Jr. wrote:
> If someone could roll a tarball for me, I could atleast make the
> skeleton for the port if not finish it off.
We should just repo copy it to ports. See how I do the setcdboot port.
--
-- David ([EMAIL PROTECTED])
To U
On Thu, 23 Aug 2001, Søren Schmidt wrote:
> It seems David O'Brien wrote:
> > diskcheckd is very annoying. Many doubt its usefulness in detecting
> > errors before it is too late. It thinks 40% of my disks are bad (which
> > I don't). I've turned it of
On Thu, Aug 23, 2001 at 10:07:15PM +0200, Søren Schmidt wrote:
> It seems David O'Brien wrote:
> > diskcheckd is very annoying. Many doubt its usefulness in detecting
> > errors before it is too late. It thinks 40% of my disks are bad (which
> > I don't). I
It seems David O'Brien wrote:
> diskcheckd is very annoying. Many doubt its usefulness in detecting
> errors before it is too late. It thinks 40% of my disks are bad (which
> I don't). I've turned it off, I know many that have.
>
> I would like to remove it from
diskcheckd is very annoying. Many doubt its usefulness in detecting
errors before it is too late. It thinks 40% of my disks are bad (which
I don't). I've turned it off, I know many that have.
I would like to remove it from the base system and put it in ports. I
really don&
> On Wed, 18 Jul 2001, Matthew Jacob wrote:
>
> > So, I took a SCSi disk away. Diskcheckd started complaining. However,
> > a camcontrol rescan couldn't make the disk go away until I killed off
> > diskcheckd, which then closed the disk, allowing the rescan to
On Thu, 19 Jul 2001 [EMAIL PROTECTED] wrote:
> > > So, I took a SCSi disk away. Diskcheckd started complaining. However,
> > > a camcontrol rescan couldn't make the disk go away until I killed off
> > > diskcheckd, which then closed the disk, allowing the rescan t
> > So, I took a SCSi disk away. Diskcheckd started complaining. However,
> > a camcontrol rescan couldn't make the disk go away until I killed off
> > diskcheckd, which then closed the disk, allowing the rescan to remove it.
> > Bad. Bad. Bad.
>
> This
On Wed, 18 Jul 2001, Matthew Jacob wrote:
> So, I took a SCSi disk away. Diskcheckd started complaining. However,
> a camcontrol rescan couldn't make the disk go away until I killed off
> diskcheckd, which then closed the disk, allowing the rescan to remove it.
> Bad. Bad. Ba
* Matthew Jacob <[EMAIL PROTECTED]> [010718 16:56] wrote:
>
> Still on by default.
In my queue then.
--
-Alfred Perlstein [[EMAIL PROTECTED]]
Ok, who wrote this damn function called '??'?
And why do my programs keep crashing in it?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscr
Still on by default.
On Wed, 18 Jul 2001, Alfred Perlstein wrote:
> * Matthew Jacob <[EMAIL PROTECTED]> [010718 16:33] wrote:
> >
> > So, I took a SCSi disk away. Diskcheckd started complaining. However,
> > a camcontrol rescan couldn't make the disk go away u
* Matthew Jacob <[EMAIL PROTECTED]> [010718 16:33] wrote:
>
> So, I took a SCSi disk away. Diskcheckd started complaining. However,
> a camcontrol rescan couldn't make the disk go away until I killed off
> diskcheckd, which then closed the disk, allowing the rescan to rem
So, I took a SCSi disk away. Diskcheckd started complaining. However,
a camcontrol rescan couldn't make the disk go away until I killed off
diskcheckd, which then closed the disk, allowing the rescan to remove it.
Bad. Bad. Bad.
ev/da4
Jul 18 14:31:15 diskcheckd[202]: error reading 512
ing normal operation. (If the disk really goes bad, it's
very likely that diskcheckd will be too late to detect it anyway.) So
for me, diskcheckd could only be useful if it would also read out the
SCSI defect lists, and compare them on a daily basis so i get an early
warning about remap activi
how, something like
!md
!acd
!cd
... hack hack hack ...
Could you test the attached patch? It allows lines like the above in
diskcheckd.conf. Seems to work but ref5 is the only current machine I
have access to which is a bit of a pain for testing things.
Stefan wrote...
>> 2) The defaults ma
Ben Smithurst <[EMAIL PROTECTED]> writes:
> I was gonna commit a fix for this, but after reporting the problem DES
> never tested the patch I supplied. :-(
I never got a patch.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freeb
> From: [EMAIL PROTECTED] (Ben Smithurst)
> Date: Wed 4 Jul, 2001
> Subject: Re: diskcheckd goes nuts on /dev/cd0
> I think excluding CDs and MDs should solve most of the problems that
> have been reported, I'm not sure what the situation with zip/jaz type
> things is tho
Ben Smithurst wrote:
> Antoine Beaupre (LMC) wrote:
>
>
>>Actually, I think that it should exclude all devices except those
>>specified in the config file... As in "check only requested disks"...
>
> It's perfectly possible to do just that...
good to hear that.
> phk wanted it to check al
Antoine Beaupre (LMC) wrote:
> Actually, I think that it should exclude all devices except those
>
> specified in the config file... As in "check only requested disks"...
It's perfectly possible to do just that... phk wanted it to check all
disks by default when I was writing it though, but th
Steven G. Kargl wrote:
> Do you need to special case tape drives, floppies, zip, etc? If so,
> you might want to exclude all devices except those that start with
> da and ad.
floppies, no:
ben@ref5:~$ grep fd0 /var/run/dmesg.boot
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
ben@ref5:~$ sysctl ke
Steven G. Kargl wrote:
> Ben Smithurst said:
>
>>Steven G. Kargl wrote:
>>>As a side question, why is diskcheckd even looking at at /dev/cd0?
>>>
>>Because my only current system when I was writing diskcheckd didn't have
>>a CD drive so I di
Ben Smithurst said:
> Steven G. Kargl wrote:
>
> > last message repeated 3 times
> > diskcheckd[213]: error reading 512 bytes from sector 0 on /dev/cd0
>
> I was gonna commit a fix for this, but after reporting the problem DES
> never tested the patch I supplied. :-
is not on a sector boundary (ssize 2048)
>
> Checking /var/log/messages I find (note date and machine name removed):
>
> diskcheckd[213]: /dev/cd0 has 2048 byte sectors, may cause minor problems
> /boot/kernel/kernel: dscheck(cd0): bio_bcount 512 is not on a sector boun
> dary (ssize 2
> From: [EMAIL PROTECTED] ("Steven G. Kargl")
> Date: Wed 4 Jul, 2001
> Subject: diskcheckd goes nuts on /dev/cd0
> However, it seems that default
> settings in diskcheckd.conf that tell diskcheckd to check
> all kern.disks in system and se
ector boundary (ssize 2048)
Checking /var/log/messages I find (note date and machine name removed):
diskcheckd[213]: /dev/cd0 has 2048 byte sectors, may cause minor problems
/boot/kernel/kernel: dscheck(cd0): bio_bcount 512 is not on a sector boun
dary (ssize 2048)
last message repeated 3 times
diskc
37 matches
Mail list logo
