All of lore.kernel.org
 help / color / mirror / Atom feed
From: fitzboy <fitzboy@iparadigms.com>
To: reiserfs-list@namesys.com
Subject: problem with reiser4
Date: Tue, 01 Mar 2005 10:54:35 -0800	[thread overview]
Message-ID: <4224BA6B.7040402@iparadigms.com> (raw)

Hello all,
I'm just switching from 2.4/reiser3 to 2.6/reiser4 on the first batch of 
machines. We are running a bunch of apple xRAIDs connected to Dell 
servers running Debian. we have the 2.6.10-mm kernel and we can make the 
reiser4 partitions, but there is a lot of lost space somewhere. If I 
create a reiser3 or xfs partition, I get 1.1T, but with reiser4 I can't 
get above 984GB. That is too much of a jump to be explained by overhead, 
so something is wrong... any thoughts?

Tim

             reply	other threads:[~2005-03-01 18:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-01 18:54 fitzboy [this message]
2005-03-01 19:07 ` problem with reiser4 Fred Schaettgen
2005-03-01 22:06   ` Hans Reiser
2005-03-13 14:46 ` Łukasz Mierzwa
2005-03-13 15:29   ` Simon Raffeiner
2005-03-23 14:57   ` Łukasz Mierzwa
  -- strict thread matches above, loose matches on Subject: below --
2005-12-15 23:40 Problem with Reiser4 Tobi Kunze
2005-12-15 23:46 ` Artur Makówka

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=4224BA6B.7040402@iparadigms.com \
    --to=fitzboy@iparadigms.com \
    --cc=reiserfs-list@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 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.