From: Vincent Danen (vdanenmandrakesoft.com)
Date: Fri Oct 03 2003 - 11:10:51 CDT

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Fri Oct 03, 2003 at 09:38:23AM +0200, Simon Oosthoek wrote:

> > > > This is what I see at the top of a syslog file:
> > > > Oct 2 04:02:00 pc021 syslogd 1.4.1: restart.
> > > > Oct 2 04:03:30 pc021 kernel: Device not ready. Make sure there is a disc
> > > > in the drive. Oct 2 04:03:30 pc021 kernel: VFS: Disk change detected on
> > > > device 08:00 Oct 2 04:03:30 pc021 kernel: sda : READ CAPACITY failed.
> > >
> > > Something that runs after logrotate in /etc/cron.daily. Probably, msec.
> > > Are you sure the disk was unmounted properly? fam sometimes locks into disks
> > > and after that umount requests fail with 'Device is in use' errors.
> > >
> > > Next time after you unmount and remove the disk, type 'mount' on the commend
> > > prompt and see what you get there.
> >
> > the pendisk is not mounted after I unmount, it stays that way when I remove
> > the disk.
> >
> > It seems likely that it is some problem with fam or msec or an interaction
> > between the two. It definately happens during the cron.daily jobs, before
> > that, there is no problem.
> >
> > I could try and disable fam and see whether this happens again...
> > I don't know what happens when I disable fam though, because I've never
> > heard what it's useful for ;-)
>
> Well, it's most definately fam related, because I wanted to try this while
> fam was disabled, so I did in xinetd.d/fam and restarted xinetd. As soon as
> I did this, the errors started coming, only with more lines:
>
> Oct 3 09:34:12 pc021 kernel: Device not ready. Make sure there is a disc in the drive.
> Oct 3 09:34:12 pc021 kernel: VFS: Disk change detected on device 08:00
> Oct 3 09:34:12 pc021 kernel: sda : READ CAPACITY failed.
> Oct 3 09:34:12 pc021 kernel: sda : status = 1, message = 00, host = 0, driver = 08
> Oct 3 09:34:12 pc021 kernel: Info fld=0xa00 (nonstd), Current sd00:00: sense key Not Ready
> Oct 3 09:34:12 pc021 kernel: sda : block size assumed to be 512 bytes, disk size 1GB.
> Oct 3 09:34:12 pc021 kernel: /dev/scsi/host0/bus0/target0/lun0: I/O error: dev 08:00, sector 0
> Oct 3 09:34:12 pc021 kernel: I/O error: dev 08:00, sector 0
> Oct 3 09:34:12 pc021 kernel: I/O error: dev 08:00, sector 2097144
> Oct 3 09:34:12 pc021 kernel: I/O error: dev 08:00, sector 2097144
> Oct 3 09:34:12 pc021 kernel: I/O error: dev 08:00, sector 0
> Oct 3 09:34:12 pc021 kernel: I/O error: dev 08:00, sector 0
> Oct 3 09:34:12 pc021 kernel: ldm_validate_partition_table(): Disk read failed.
> Oct 3 09:34:12 pc021 kernel: I/O error: dev 08:00, sector 0
>
> As soon as I plugged the disk in again, this stopped.
>
> I guess this is a fam bug or a bug of something that depends on fam....

Can you file a bug against fam on bugs.mandrakelinux.com for whatever
version of Mandrake you're using (I forget which one you're using)? Maybe
we can get the maintainer to fix this.

--
MandrakeSoft Security; http://www.mandrakesecure.net/
Online Security Resource Book; http://linsec.ca/
"lynx -source http://linsec.ca/vdanen.asc | gpg --import"
{FE6F2AFD : 88D8 0D23 8D4B 3407 5BD7 66F9 2043 D0E5 FE6F 2AFD}

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (Darwin)

iD8DBQE/fZ+LIEPQ5f5vKv0RAi2nAJ9QeJoyE1/QHxKX0w3vYkULmqJsYACfa7aY
ZRQLeYcYNYV4m+fwmZpjoww=
=SEcx
-----END PGP SIGNATURE-----

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]