From: Petr Sebor <petr@scssoft.com>
To: Nikita Danilov <Nikita@Namesys.COM>
Cc: linux-kernel@vger.kernel.org
Subject: Re: incorrect inode count on reiserfs
Date: Mon, 08 Dec 2003 15:06:21 +0100 [thread overview]
Message-ID: <3FD4855D.4090203@scssoft.com> (raw)
In-Reply-To: <16340.33245.887082.96412@laputa.namesys.com>
Nikita Danilov wrote:
>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.
>
>
duh, I thought that f_files is applicable to reiserfs as well...
>Fix would really be simple: ignore test results if ->f_files is 0 or
>0xffffffff.
>
>
ok, sorry for the noise... as for the inn2, I have disabled the free
inode check in innwatch.ctl and it works well
thanks!
Petr
next prev parent reply other threads:[~2003-12-08 14:06 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 [this message]
2003-12-08 14:11 ` Andreas Schwab
2003-12-08 14:35 ` Erik Hensema
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=3FD4855D.4090203@scssoft.com \
--to=petr@scssoft.com \
--cc=Nikita@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox