All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David Gómez" <david@pleyades.net>
To: Robert Love <rml@novell.com>
Cc: John McCutchan <ttb@tentacle.dhs.org>,
	Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Problem with inotify
Date: Thu, 30 Jun 2005 20:38:29 +0200	[thread overview]
Message-ID: <20050630183829.GB1108@fargo> (raw)
In-Reply-To: <1120156188.6745.103.camel@betsy>

Hi Robert,

On Jun 30 at 02:29:48, Robert Love wrote:
> > I just patched 2.6.12 kernel with the inotify latest patch
> > (inotify-0.23-rml-2.6.12-14.patch). Inotify is working ok with the test program
> > provided in inotify-utils but... I can no longer mount my IDE cdrom devices
> > :(. Each time i try to mount a disc, the mount proccess get stuck in D state. I
> > don't see what's the relation between inotify and IDE devices, but if i switch
> > back to the unpatched 2.6.12, mounting works again.
> 
> Very weird.

Indeed.

> Did everything work with an earlier inotify?

It's the first notify i've tested, so i cannot compare with previous versions.

> Does wchan show anything useful (ps -ewo user,pid,command,wchan)?

I have to reboot to test it. I'll do it and told you if i see anything
weird in wchan for the mount process.

> Does it mount successfully once, and then subsequent mounts get suck, or
> does even the first mount get stuck in D?

The first mount get stuck, and subsequent mounts too. I tried to mount my CD-writer
and after that my DVD-writer and i got two mount D processes.

Thanks for the quick answer ;)

-- 
David Gómez                                      Jabber ID: davidge@jabber.org

  reply	other threads:[~2005-06-30 18:41 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-30 18:18 Problem with inotify David Gómez
2005-06-30 18:29 ` Robert Love
2005-06-30 18:38   ` David Gómez [this message]
2005-06-30 19:33   ` David Gómez
2005-06-30 20:39     ` Anton Altaparmakov
2005-06-30 20:48       ` David Gómez
2005-06-30 22:35         ` Anton Altaparmakov
2005-07-01 20:25           ` Robert Love
2005-07-02 12:54             ` David Gómez
2005-07-02 16:25               ` Robert Love
2005-07-02  9:12           ` Daniel Drake
2005-07-02 22:09             ` Anton Altaparmakov
2005-07-02 23:38               ` Daniel Drake
2005-07-03  0:08                 ` Anton Altaparmakov
2005-07-03 10:34                   ` Daniel Drake
2005-07-04 14:27                     ` Anton Altaparmakov
2005-07-04 14:39                       ` Anton Altaparmakov
2005-07-04 15:12                         ` Anton Altaparmakov
2005-07-04 15:55                           ` Gautam Singaraju
2005-07-04 16:00                             ` Anton Altaparmakov
2005-07-04 17:57                       ` Daniel Drake
2005-07-04 19:09                         ` Anton Altaparmakov
2005-07-05  1:33                           ` John McCutchan
2005-07-05  7:56                             ` Anton Altaparmakov
2005-07-05 15:48                               ` John McCutchan
2005-07-05 17:06                                 ` Anton Altaparmakov
2005-07-05 18:07                                   ` John McCutchan
2005-07-05 20:53                                     ` Anton Altaparmakov

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=20050630183829.GB1108@fargo \
    --to=david@pleyades.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rml@novell.com \
    --cc=ttb@tentacle.dhs.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.