From: Andreas Dilger <adilger@clusterfs.com>
To: Clifford Beshers <clifford.beshers@lindows.com>
Cc: Hans Reiser <reiser@namesys.com>,
Vladimir Saveliev <vs@namesys.com>,
Reiserfs mail-list <Reiserfs-List@namesys.com>,
Vitaly Fertman <vitaly@namesys.com>
Subject: Re: 2 Terabyte install
Date: Tue, 11 May 2004 21:41:50 -0600 [thread overview]
Message-ID: <20040512034150.GS9641@schnapps.adilger.int> (raw)
In-Reply-To: <40A19147.4010703@lindows.com>
On May 11, 2004 19:51 -0700, Clifford Beshers wrote:
> Thanks for the help everyone. In the end, it turned out that sfdisk is
> indeed the culprit. We created a 2.1T partition with fdisk, then asked
> sfdisk for the size and it said: -92,xxx,xxx. Unfortunately, this means
> we have to either fix it or find an alternate solution to creating
> partitions. If the word ``parted'' is on the tip of your tongue I'll
> bet you haven't actually used the thing...
>
> There were a few bugs of ours that acted as red herrings, but Linspire
> is now up and running on this system with ReiserFS 3 and kernel 2.6.5.
>
> While I'm here, I have some other questions:
>
> * What is the time complexity of mounting a ReiserFS partition? It
> seems to be proportional to the size of the partition? Is it
> different for Reiser4?
AFAIK, reiserfs will do the initial zeroing of the journal and filesystem
bitmaps at the first mount time instead of at mkreiserfs time. I don't
know why it was done that way.
> * Is there a tool to determine the type of file system on a
> partition without mounting it?
Lots of them. "file -s /dev/foo" or if you have a newer e2fsprogs (1.33
and newer I think) you can use "blkid [dev ...]" to tell you a bunch of
things about each device (LABEL, UUID, TYPE).
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
next prev parent reply other threads:[~2004-05-12 3:41 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-06 22:58 2 Terabyte install Clifford Beshers
2004-05-07 8:18 ` Vladimir Saveliev
2004-05-07 16:17 ` Hans Reiser
2004-05-07 16:48 ` Clifford Beshers
2004-05-07 17:38 ` Lamont R. Peterson
2004-05-10 16:53 ` Hans Reiser
2004-05-11 15:23 ` Vladimir Karavelov
2004-05-12 2:51 ` Clifford Beshers
2004-05-12 3:41 ` Andreas Dilger [this message]
2004-05-12 6:51 ` Vladimir Saveliev
2004-05-12 7:06 ` Philippe Gramoullé
2004-05-12 23:22 ` Clifford Beshers
2004-05-12 23:36 ` Clifford Beshers
2004-05-12 16:59 ` Hans Reiser
2004-05-12 18:24 ` Mike Benoit
2004-05-12 18:36 ` Chris Mason
2004-05-12 18:30 ` Clifford Beshers
2004-05-13 5:43 ` Hans Reiser
2004-05-13 20:04 ` Paul Wagland
2004-05-13 20:11 ` mjt
2004-05-16 17:07 ` Namesys now accepts Visa cards on our website (support questions and donations both) Hans Reiser
2004-05-16 17:22 ` mjt
2004-05-16 17:43 ` Hans Reiser
2004-05-17 8:24 ` Domenico Andreoli
2004-05-20 18:22 ` Redeeman
2004-05-20 18:37 ` mjt
2004-05-20 18:55 ` Redeeman
2004-05-15 21:28 ` 2 Terabyte install Hans Reiser
2004-05-20 18:24 ` Redeeman
2004-05-07 17:44 ` Lamont R. Peterson
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=20040512034150.GS9641@schnapps.adilger.int \
--to=adilger@clusterfs.com \
--cc=Reiserfs-List@namesys.com \
--cc=clifford.beshers@lindows.com \
--cc=reiser@namesys.com \
--cc=vitaly@namesys.com \
--cc=vs@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.