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: Fri, 07 May 2004 09:48:09 -0700 [thread overview]
Message-ID: <409BBDC9.3030809@lindows.com> (raw)
In-Reply-To: <409BB690.6030604@namesys.com>
Thanks Hans, but no need. I found the page in the FAQ about three
minutes after I posted. I get so used to google finding me the right
things, I occasionally forget to just go to the place I know should have
the answers.
So far, I know that sfdisk choked on creating the partition, but that
fdisk succeeded. After that the install proceeded normally, but the
system didn't reboot. I have to go get details on why, but my guessis
either lilo or a missing module in the initrd.
Hans Reiser wrote:
> Vladimir Saveliev wrote:
>
>> Hello
>>
>> On Fri, 2004-05-07 at 02:58, Clifford Beshers wrote:
>>
>>
>>> What are the current size limitations for disks/partitions/filesystems
>>> with the following combinations? My googling has produced
>>> inconsistent answers.
>>> { linux 2.4.24, linux 2.6.5 } X { reiserfs3, reiser4 }
>>>
>>
>>
>> http://namesys.com/faq.html#reiserfsspecs
>>
>>
>>
>>> We have a new machine with a 3-ware 8 port controller (looks like a
>>> scsi controller to the system, but actually drives 8 ide drives). We
>>> have 8 x 300GB drives attached for a total > 2TB.
>>>
>>> Our IT guy has been unable to install Linspire on it (linux 2.6.5,
>>> reiserfs3). I'm about to go look in more detail, but I thought I'd
>>> find out what the bounds were for sure.
>>>
>>>
>>
>>
>> I assume mkreiserfs was not the reason why you guys failed to install
>> linux on your hardware. It works for > 2tb devices.
>>
>>
>>
>>> Thanks,
>>>
>>> Cliff
>>>
>>> --
>>>
>>> This message contains information which may be confidential and
>>> privileged. Unless you are the addressee (or authorized to receive
>>> for the addressee), you may not use, copy or disclose to anyone the
>>> message or any information contained in the message. If you have
>>> received the message in error, please advise the sender and delete
>>> the message. Thank you.
>>>
>>
>>
>>
>>
>>
>>
> Please provide exact answer to this question about what are V3
> limits. Vitaly, please assist.
next prev parent reply other threads:[~2004-05-07 16:48 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 [this message]
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
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=409BBDC9.3030809@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.