From: Hans Reiser <reiser@namesys.com>
To: "Robert L. Harris" <Robert.L.Harris@rdlg.net>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>,
Oleg Drokin <green@namesys.com>
Subject: Re: inode problem?
Date: Thu, 26 Jun 2003 20:25:38 +0400 [thread overview]
Message-ID: <3EFB1E82.2050907@namesys.com> (raw)
In-Reply-To: <20030626152946.GN21580@rdlg.net>
Robert L. Harris wrote:
> I have a system at work that seems to have an ext3 filesystem made
>with -T largefile when it really shouldn't have and is running low on
>inodes. A co-worker has mentioned that reiserfs doesn't have inode
>problems. I tried to look this up but am having problems
>verifying/denying this:
>
>{0}:Documentation>host www.reiserfs.org
>www.reiserfs.org does not exist, try again
>
>Whois also doesn't return anything. Anyone have any proof either way
>and news on the current stability of reiserfs in the 2.4.21 tree?
>
>Robert
>
>
>:wq!
>---------------------------------------------------------------------------
>Robert L. Harris | GPG Key ID: E344DA3B
> @ x-hkp://pgp.mit.edu
>DISCLAIMER:
> These are MY OPINIONS ALONE. I speak for no-one else.
>
>Diagnosis: witzelsucht
>
>IPv6 = robert@ipv6.rdlg.net http://ipv6.rdlg.net
>IPv4 = robert@mail.rdlg.net http://www.rdlg.net
>
>
inodes are yucky yucky.;-) We ain't got none.
--
Hans
next prev parent reply other threads:[~2003-06-26 16:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-26 15:29 inode problem? Robert L. Harris
2003-06-26 15:41 ` Nikita Danilov
2003-06-26 16:50 ` [OT] " Christian Kujau
2003-06-26 16:59 ` Nikita Danilov
2003-06-26 17:31 ` Carl-Daniel Hailfinger
2003-06-26 16:25 ` Hans Reiser [this message]
2003-06-26 16:26 ` Hans Reiser
-- strict thread matches above, loose matches on Subject: below --
2003-06-26 20:10 burnt_2
2003-06-29 11:21 ` Hans Reiser
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=3EFB1E82.2050907@namesys.com \
--to=reiser@namesys.com \
--cc=Robert.L.Harris@rdlg.net \
--cc=green@namesys.com \
--cc=linux-kernel@vger.kernel.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.