From: Jens Axboe <axboe@suse.de>
To: "Richard B. Johnson" <root@chaos.analogic.com>
Cc: Holluby István <holluby@interware.hu>, linux-kernel@vger.kernel.org
Subject: Re: mke2fs /dev/loop0
Date: Wed, 28 Feb 2001 16:41:51 +0100 [thread overview]
Message-ID: <20010228164151.H21518@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.33.0102281545120.1836-100000@cica.khb.hu> <Pine.LNX.3.95.1010228102221.4469A-100000@chaos.analogic.com>
In-Reply-To: <Pine.LNX.3.95.1010228102221.4469A-100000@chaos.analogic.com>; from root@chaos.analogic.com on Wed, Feb 28, 2001 at 10:31:35AM -0500
On Wed, Feb 28 2001, Richard B. Johnson wrote:
> `mke2fs /dev/loop0` requires an additional parameter (file size to
> create). Otherwise, it will try to use all the RAM in your system, plus...
>
> If it worked before, it was because of luck. FYI, this is not the
> way to create a ramdisk. Normally you use the loop device to mount
> a file as a file-system, i.e., `mount -o loop filename /mnt`.
> So, I don't know what you are trying to do except crash your system.
This could not be more wrong. mke2fs will query the size of the
loop device, and make the correct size file system regardless
of whether it's file or block device backed. And it will not
try to use all RAM in the system?! This is loop, not a ramdisk.
Dirty buffers will be flushed to loop like any other block
device in the system, if that doesn't work then we have a mm
bug.
The previous answer was right -- loop has been broken for quite
some time, but use -ac latest on top of 2.4.2 and it should work
flawlessly for you.
--
Jens Axboe
next prev parent reply other threads:[~2001-02-28 15:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-28 15:07 mke2fs /dev/loop0 Holluby
2001-02-28 13:35 ` Arnaldo Carvalho de Melo
2001-02-28 15:31 ` Richard B. Johnson
2001-02-28 15:41 ` Jens Axboe [this message]
2001-02-28 16:16 ` Richard B. Johnson
2001-02-28 16:23 ` Jens Axboe
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=20010228164151.H21518@suse.de \
--to=axboe@suse.de \
--cc=holluby@interware.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.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.