public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Padraig Brady <padraig@antefacto.com>
To: andersen@codepoet.org
Cc: Matthias Andree <matthias.andree@stud.uni-dortmund.de>,
	Linux-Kernel mailing list <linux-kernel@vger.kernel.org>,
	sopwith@redhat.com, otaylor@redhat.com
Subject: Re: Need help tracing regular write activity in 5 s interval
Date: Wed, 05 Jun 2002 15:08:56 +0100	[thread overview]
Message-ID: <3CFE1B78.9010406@antefacto.com> (raw)
In-Reply-To: <20020602135501.GA2548@merlin.emma.line.org> <3CFCA2B0.4060501@antefacto.com> <20020604120434.GA1386@codepoet.org>

I'm sure it will :-)

However this it just masking the "problem", and I don't
think it's "buggy CDROM drives" as I've tried 3 different
machines with the following drives:

SAMSUNG DVD-ROM SD-612
TOSHIBA DVD-ROM SD-C2402
CREATIVE CD5233E

and they all show the same problem. I.E. logs filling with
"VFS: Disk change detected on device ide1(22,0)".

magicdev essentially does:

while (1) {
     cd = open ("/dev/cdrom", O_RDONLY|O_NONBLOCK);
     if (ioctl (cd, CDROM_DRIVE_STATUS, CDSL_CURRENT) == CDS_DISC_OK) {
         /* do stuff */
     }
     close(cd);
     sleep(2);
}

Note, it's the open() that causes the check_media_changed(),
so why does this always return true? Is there a way you
can turn it it off? echoing [01] to /proc/sys/dev/cdrom/check_media
made no difference.

Also related, why does the LED flash on every ATA command?
Is this controlled by the drive or ide controller?
Are you telling me that windows would flash the LED every so often
to automount CDs?

thanks,
Padraig.

Erik Andersen wrote:
> On Tue Jun 04, 2002 at 12:21:20PM +0100, Padraig Brady wrote:
> 
>>As an aside, Nautilus (1.0.4) does stuff every 2 seconds
>>(checking is there a CD inserted) that causes the disk LED to flash.
>>The same action also causes the kernel (2.4.13) to fill up the ring
>>buffer with: "VFS: Disk change detected on device ide1(22,0)".
> 
> 
> This should fix the symptom...
> 
> --- linux/fs/block_dev.c.orig	Tue Jun  4 06:03:44 2002
> +++ linux/fs/block_dev.c	Tue Jun  4 06:03:44 2002
> @@ -582,8 +582,11 @@
>  	if (!bdops->check_media_change(dev))
>  		return 0;
>  
> +	#if 0
> +	/* Polling buggy CD-ROM drives can fill the logs.  Make it shutup. */
>  	printk(KERN_DEBUG "VFS: Disk change detected on device %s\n",
>  		bdevname(dev));
> +	#endif
>  
>  	sb = get_super(dev);
>  	if (sb && invalidate_inodes(sb))
>  -Erik
> 
> --
> Erik B. Andersen             http://codepoet-consulting.com/
> --This message was written using 73% post-consumer electrons--




  reply	other threads:[~2002-06-05 14:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-02 13:55 Need help tracing regular write activity in 5 s interval Matthias Andree
2002-06-04 11:21 ` Padraig Brady
2002-06-04 11:41   ` Muli Ben-Yehuda
2002-06-04 11:43   ` Xavier Bestel
2002-06-04 12:04   ` Erik Andersen
2002-06-05 14:08     ` Padraig Brady [this message]
2002-06-05 15:13       ` Padraig Brady
2002-06-05 15:50       ` Owen Taylor
2002-06-05 16:43         ` Padraig Brady
2002-06-05 22:22           ` Padraig Brady
  -- strict thread matches above, loose matches on Subject: below --
2002-06-02 15:25 Thunder from the hill
2002-06-02 15:41 ` Kevin Krieser
2002-06-02 16:12 ` Kenneth Johansson
2002-06-02 20:19 ` Matthias Andree

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=3CFE1B78.9010406@antefacto.com \
    --to=padraig@antefacto.com \
    --cc=andersen@codepoet.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthias.andree@stud.uni-dortmund.de \
    --cc=otaylor@redhat.com \
    --cc=sopwith@redhat.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