linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Petr Sebor <petr@scssoft.com>
To: linux-kernel@vger.kernel.org
Subject: incorrect inode count on reiserfs
Date: Mon, 08 Dec 2003 14:26:20 +0100	[thread overview]
Message-ID: <3FD47BFC.9020008@scssoft.com> (raw)

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)

2.6.0-test11:
df -i:

Filesystem            Inodes   IUsed   IFree IUse% Mounted on
/dev/sda1                  0       0       0    -  /
/dev/sdb1                  0       0       0    -  /mnt/sdb1

while df shows:
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/sda1            243208608  11069612 232138996   5% /
/dev/sdb1             36150172     32840  36117332   1% /mnt/sdb1

different reiserfs based machine with 2.4.23; this is where the inn2
used to work before, but the inode test was not failing because of the
'always-nonzero' inode count:

df -i
Filesystem            Inodes   IUsed   IFree IUse% Mounted on
/dev/hde1            4294967295       0 4294967295    0% /
/dev/hdg1            4294967295       0 4294967295    0% /mnt/d2

df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/hde1             77634256  77092844    541412 100% /
/dev/hdg1             38586912  19156508  19430404  50% /mnt/d2

another 2.6.0-test11 machine with ext2 reports inode counts correctly. 
my assumption is
that the problem is somehow reiserfs related, but my knowledge ends here.
all reiser fs's are of version 3.6

any ideas?

Petr


             reply	other threads:[~2003-12-08 13:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-08 13:26 Petr Sebor [this message]
2003-12-08 13:51 ` incorrect inode count on reiserfs Nikita Danilov
2003-12-08 14:06   ` Petr Sebor
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=3FD47BFC.9020008@scssoft.com \
    --to=petr@scssoft.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;
as well as URLs for NNTP newsgroup(s).