From: Philippe Troin <phil@fifi.org>
To: Aroop MP <aroop@poornam.com>
Cc: Dimitri Sivanich <sivanich@sgi.com>,
manfred@colorfullife.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, lse-tech@lists.sourceforge.net
Subject: Re: lsattr: Inappropriate ioctl for device While reading flags!!!
Date: 26 Jul 2004 23:40:57 -0700 [thread overview]
Message-ID: <874qnueyva.fsf@ceramic.fifi.org> (raw)
In-Reply-To: <200407270741.44003.aroop@poornam.com>
Aroop MP <aroop@poornam.com> writes:
> Hi,
>
> Thanks for your quick reply. When i check lsattr of the file
> /usr/local/cpanel/3rdparty/etc/php.ini i got the following error.
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Server[~]# lsattr /usr/local/cpanel/3rdparty/etc/php.ini
> lsattr: Inappropriate ioctl for device While reading flags on
> /usr/local/cpanel/3rdparty/etc/php.ini
> Server[~]#
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> Please get back to me if you need any more info. regarding this.
Because /usr/local/cpanel/3rdparty/etc/php.ini is not on an ext[23]
filesystem? Remote mounting via NFS, or your favorite network fs does
not count as ext[23].
Phil.
WARNING: multiple messages have this Message-ID (diff)
From: Philippe Troin <phil@fifi.org>
To: Aroop MP <aroop@poornam.com>
Cc: Dimitri Sivanich <sivanich@sgi.com>,
manfred@colorfullife.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, lse-tech@lists.sourceforge.net
Subject: Re: lsattr: Inappropriate ioctl for device While reading flags!!!
Date: 26 Jul 2004 23:40:57 -0700 [thread overview]
Message-ID: <874qnueyva.fsf@ceramic.fifi.org> (raw)
In-Reply-To: <200407270741.44003.aroop@poornam.com>
Aroop MP <aroop@poornam.com> writes:
> Hi,
>
> Thanks for your quick reply. When i check lsattr of the file
> /usr/local/cpanel/3rdparty/etc/php.ini i got the following error.
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Server[~]# lsattr /usr/local/cpanel/3rdparty/etc/php.ini
> lsattr: Inappropriate ioctl for device While reading flags on
> /usr/local/cpanel/3rdparty/etc/php.ini
> Server[~]#
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> Please get back to me if you need any more info. regarding this.
Because /usr/local/cpanel/3rdparty/etc/php.ini is not on an ext[23]
filesystem? Remote mounting via NFS, or your favorite network fs does
not count as ext[23].
Phil.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2004-07-27 6:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-23 19:05 [PATCH] Locking optimization for cache_reap Dimitri Sivanich
2004-07-23 19:05 ` Dimitri Sivanich
2004-07-27 1:01 ` Andrew Morton
2004-07-27 1:01 ` Andrew Morton
2004-07-27 1:47 ` Dimitri Sivanich
2004-07-27 1:47 ` Dimitri Sivanich
2004-07-27 1:59 ` Aroop MP
2004-07-27 1:59 ` Aroop MP
[not found] ` <20040727020338.GB23967@sgi.com>
2004-07-27 2:11 ` lsattr: Inappropriate ioctl for device While reading flags!!! Aroop MP
2004-07-27 2:11 ` Aroop MP
2004-07-27 6:40 ` Philippe Troin [this message]
2004-07-27 6:40 ` Philippe Troin
2004-07-27 2:01 ` [PATCH] Locking optimization for cache_reap Dimitri Sivanich
2004-07-27 2:01 ` Dimitri Sivanich
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=874qnueyva.fsf@ceramic.fifi.org \
--to=phil@fifi.org \
--cc=aroop@poornam.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=manfred@colorfullife.com \
--cc=sivanich@sgi.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 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.