From: "Martin Schlemmer [c]" <azarah@nosferatu.za.org>
To: John McCutchan <ttb@tentacle.dhs.org>
Cc: Linux Kernel Mailing Lists <linux-kernel@vger.kernel.org>,
nautilus-list@gnome.org, gamin-list@gnome.org, rml@ximian.com,
viro@parcelfarce.linux.theplanet.co.uk
Subject: Re: [RFC][PATCH] inotify 0.8.1 [u]
Date: Mon, 23 Aug 2004 21:44:19 +0200 [thread overview]
Message-ID: <1093290259.9495.18.camel@nosferatu.lan> (raw)
In-Reply-To: <1092889961.31314.3.camel@vertex>
[-- Attachment #1: Type: text/plain, Size: 1135 bytes --]
On Thu, 2004-08-19 at 06:32, John McCutchan wrote:
Hi
> I am resubmitting inotify for comments and review. Inotify has
> changed drastically from the earlier proposal that Al Viro did not
> approve of. There is no longer any use of (device number, inode number)
> pairs. Please give this version of inotify a fresh view.
>
I applied this to 2.6.8.1 and most of -mm4's patches - it applied
cleanly and compiled fine.
I use devicemapper to stripe two 80gb sata drives on intel sata
controller, using initramfs.
Now when I boot, I see something like:
---
BIOS EDD facility v0.16 2004-Jun-25, 2 devices found
Freeing unused kernel memory: 264k freed
inotify device opened
dm ioctl error or such
---
Which then results in a panic as the dm volumes cannot be setup
and no / found by kernel. So basically it seems like inotify
mess with dm in some way or other - any quick ideas what it
could be?
I do not have serial console, so if you need a more complete log,
just let me know from where abouts I should start, and if any
debugging should be turned on, etc.
Thanks,
--
Martin Schlemmer
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-08-23 20:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-19 4:32 [RFC][PATCH] inotify 0.8.1 John McCutchan
2004-08-23 19:44 ` Martin Schlemmer [c] [this message]
2004-08-24 1:04 ` [RFC][PATCH] inotify 0.8.1 [u] John McCutchan
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=1093290259.9495.18.camel@nosferatu.lan \
--to=azarah@nosferatu.za.org \
--cc=gamin-list@gnome.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nautilus-list@gnome.org \
--cc=rml@ximian.com \
--cc=ttb@tentacle.dhs.org \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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.