From: Erik Mouw <erik@harddisk-recovery.com>
To: "Masthan, Dudekula (STSD)" <dudekula.masthan@hp.com>
Cc: "Vladimir V. Saveliev" <vs@namesys.com>,
reiserfs-list@namesys.com, linux-fsdevel@vger.kernel.org
Subject: Re: BUG IN REISERFS
Date: Fri, 30 Jun 2006 14:29:06 +0200 [thread overview]
Message-ID: <20060630122906.GE11568@harddisk-recovery.com> (raw)
In-Reply-To: <4EEB5A4713E61F49A759A504BECCBC0A028D1CCB@bgeexc01.asiapacific.cpqcorp.net>
Please choose your subject carefully. Claiming that you found a bug in
reiserfs while you only met a boundary condition isn't very polite.
On Fri, Jun 30, 2006 at 05:51:14PM +0530, Masthan, Dudekula (STSD) wrote:
> Mkreiserfs command is failing by showing " There are no enoguh blocks on
> this device" , What is the minimum size of a disk to create reiserfs
> file system
That mainly depends on the journal size. The default journal size is 32
MB which means that an actual useful disk size is about 100 MB. See
mkreiserfs(8), -s option.
Erik
--
+-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 --
| Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands
next prev parent reply other threads:[~2006-06-30 12:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-30 5:38 BUG IN REISERFS SLES 10 : Masthan, Dudekula (STSD)
2006-06-30 5:38 ` Masthan, Dudekula (STSD)
2006-06-30 9:11 ` Vladimir V. Saveliev
2006-06-30 12:21 ` BUG IN REISERFS Masthan, Dudekula (STSD)
2006-06-30 12:21 ` Masthan, Dudekula (STSD)
2006-06-30 12:29 ` Erik Mouw [this message]
2006-06-30 13:36 ` Vladimir V. Saveliev
2006-06-30 16:52 ` Hans Reiser
-- strict thread matches above, loose matches on Subject: below --
2005-10-17 12:53 Bug in reiserfs Jesús Malo Poyatos
2001-09-01 8:54 Bug in ReiserFS Aleksander Adamowski
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=20060630122906.GE11568@harddisk-recovery.com \
--to=erik@harddisk-recovery.com \
--cc=dudekula.masthan@hp.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=reiserfs-list@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.