From: Erik Hensema <erik@hensema.net>
To: linux-kernel@vger.kernel.org
Subject: Re: incorrect inode count on reiserfs
Date: Mon, 8 Dec 2003 14:35:47 +0000 (UTC) [thread overview]
Message-ID: <slrnbt9322.27h.erik@bender.home.hensema.net> (raw)
In-Reply-To: 16340.33245.887082.96412@laputa.namesys.com
Nikita Danilov (Nikita@Namesys.COM) wrote:
> Petr Sebor writes:
> > I have noticed this behavior when moving the inn2 news server to
> > 2.6.0-test11 kernel
> > from 2.4.23
> > (inn2 refuses to start because if free inode shortage)
[...]
> reiserfs has no fixed predefined number of inodes on the file
> system. Hence, field f_files of struct statfs (see man 2 statfs) is not
> applicable to this file system. Man page explicitly says:
>
> Fields that are undefined for a particular file system are
> set to 0.
>
> Previous man page stated that file system should put -1 (4294967295)
> into undefined fields. Reiserfs has been changed to conform to the
> changed specification.
[...]
> Fix would really be simple: ignore test results if ->f_files is 0 or
> 0xffffffff.
But innwatch checks for a out-of-inodes condition. How can it differentiate
between a undefined number of inodes (field set to 0) and a system that ran
out of inodes (field dropped to 0)?
A '4294967295 inodes should be enough for anyone'-situation is preferable I
think.
--
Erik Hensema <erik@hensema.net>
next prev parent reply other threads:[~2003-12-08 14:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-08 13:26 incorrect inode count on reiserfs Petr Sebor
2003-12-08 13:51 ` Nikita Danilov
2003-12-08 14:06 ` Petr Sebor
2003-12-08 14:11 ` Andreas Schwab
2003-12-08 14:35 ` Erik Hensema [this message]
2003-12-08 15:33 ` Nikita Danilov
2003-12-08 16:09 ` Matthias Urlichs
2003-12-08 17:24 ` Erik Hensema
2003-12-09 3:01 ` Herbert Poetzl
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=slrnbt9322.27h.erik@bender.home.hensema.net \
--to=erik@hensema.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).