public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tupshin Harper <tupshin@tupshin.com>
To: Alex Zarochentsev <zam@namesys.com>
Cc: Steven Cole <elenstev@mesatop.com>,
	Hans Reiser <reiser@namesys.com>, Oleg Drokin <green@namesys.com>,
	reiserfs-dev@namesys.com, reiserfs-list@namesys.com,
	linux-kernel@vger.kernel.org, demidov <demidov@namesys.com>,
	god@namesys.com
Subject: Re: reiser4 snapshot for August 26th.
Date: Thu, 28 Aug 2003 09:33:30 -0700	[thread overview]
Message-ID: <3F4E2EDA.3060508@tupshin.com> (raw)
In-Reply-To: <20030828114654.GA1361@backtop.namesys.com>

Alex Zarochentsev wrote:

>On Tue, Aug 26, 2003 at 01:14:46PM -0600, Steven Cole wrote:
>  
>
>>df: `/share_r4': Value too large for defined data type
>>    
>>
>
>I can't reproduce that.  Do you see df errors each time you mount just created
>reiser4 fs?  Can you provide additional information about your system:
>distro, libc which you used?  
>
>My hypothesysis is that libc statfs or df itself want to convert "free inodes"
>result parameter which is __u64 to shorter data type.  reiser4_statfs() sets
>kstatfs->f_ffree to a large value which is close to 2^64.
>  
>
This problem is 100% reproducible for me.

mkfs.reiser4
mount
df

immediately shows the problem.

Running Debian Sid, stock kernel 2.6.0-test4 + Aug 26 reiser4 snapshot, 
Athlon XP CPU, glibc-2.3.1.

-Tupshin


  parent reply	other threads:[~2003-08-28 16:33 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-26 10:22 reiser4 snapshot for August 26th Oleg Drokin
2003-08-26 18:20 ` Steven Cole
2003-08-26 18:26   ` Alex Zarochentsev
2003-08-26 19:36     ` Felipe Alfaro Solana
2003-08-26 19:43       ` Oleg Drokin
2003-08-26 19:51         ` Steven Cole
2003-08-26 20:05           ` Mike Fedyk
2003-08-26 20:13             ` Steven Cole
2003-08-26 20:26               ` Mike Fedyk
2003-08-26 20:25                 ` Steven Cole
2003-08-26 20:30                 ` Hans Reiser
2003-08-26 20:28           ` Hans Reiser
2003-08-26 19:53         ` Mike Fedyk
2003-08-26 19:57       ` how to log reiser and raid0 crash? 2.6.0-t4 Resident Boxholder
2003-08-26 22:20         ` Resident Boxholder
2003-08-27 10:35         ` Oleg Drokin
2003-08-28  7:28           ` Resident Boxholder
2003-08-26 18:38   ` reiser4 snapshot for August 26th Steven Cole
2003-08-26 19:22     ` Hans Reiser
2003-08-26 18:38   ` Oleg Drokin
2003-08-26 18:41   ` Hans Reiser
2003-08-26 18:41     ` Alex Zarochentsev
2003-08-26 19:14       ` Steven Cole
2003-08-28 11:46         ` Alex Zarochentsev
2003-08-28 15:12           ` Steven Cole
2003-08-28 16:33           ` Tupshin Harper [this message]
2003-08-26 19:15       ` Hans Reiser
2003-08-28 18:31   ` Vladimir Demidov
2003-08-26 21:28 ` Diego Calleja García
2003-08-27  7:38   ` Oleg Drokin
2003-08-27  5:52 ` Ian Wienand
2003-08-27  6:03   ` Yury Umanets
2003-08-27 11:19     ` Felipe Alfaro Solana
2003-08-27 15:54       ` Hans Reiser
2003-09-15 11:15 ` reiser4 snapshot 20030905 [OOPS] Maciej Soltysiak
2003-09-15 13:52   ` Nikita Danilov

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=3F4E2EDA.3060508@tupshin.com \
    --to=tupshin@tupshin.com \
    --cc=demidov@namesys.com \
    --cc=elenstev@mesatop.com \
    --cc=god@namesys.com \
    --cc=green@namesys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reiser@namesys.com \
    --cc=reiserfs-dev@namesys.com \
    --cc=reiserfs-list@namesys.com \
    --cc=zam@namesys.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox