From: Clifford Beshers <clifford.beshers@lindows.com>
To: Hans Reiser <reiser@namesys.com>
Cc: Vladimir Saveliev <vs@namesys.com>,
Reiserfs mail-list <Reiserfs-List@namesys.com>,
Vitaly Fertman <vitaly@namesys.com>
Subject: Re: 2 Terabyte install
Date: Wed, 12 May 2004 11:30:29 -0700 [thread overview]
Message-ID: <40A26D45.2010707@lindows.com> (raw)
In-Reply-To: <40A257DA.2010903@namesys.com>
Hans Reiser wrote:
> 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.
>
>
> We can probably fix it for you if you like....
I'm going to try the alternatives first and at the same time email the
author and the Debian maintainer of sfdisk and ask them what's up.
>
>> 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?
>>
> is the time a problem in practice, or just a curiousity point?
Our customers have complained about our boot times, so we've been
tracking things down and fixing them. We were doing two passes of
mounting everything, one pass to figure out what was there, another to
let the traditional 'mountall' init script do its work. We were
assuming that the mount times were constant and small. But as the disks
are getting bigger, the second mount is noticeable, so we're fixing
that. The first mount is definitely noticeable on the 2T machine, but
we figure if we do our jobs right, people should rarely be rebooting anyway.
Cliff
next prev parent reply other threads:[~2004-05-12 18:30 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
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 [this message]
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=40A26D45.2010707@lindows.com \
--to=clifford.beshers@lindows.com \
--cc=Reiserfs-List@namesys.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.