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 17:23:45 +0100 [thread overview]
Message-ID: <20010228172345.K21518@suse.de> (raw)
In-Reply-To: <20010228164151.H21518@suse.de> <Pine.LNX.3.95.1010228111048.5030A-100000@chaos.analogic.com>
In-Reply-To: <Pine.LNX.3.95.1010228111048.5030A-100000@chaos.analogic.com>; from root@chaos.analogic.com on Wed, Feb 28, 2001 at 11:16:02AM -0500
On Wed, Feb 28 2001, Richard B. Johnson wrote:
> Wrong. The report showed a response to a command. Nothing was reported
> to have been mounted through the loop device. Instead, the raw command
> `mke2fs /dev/loop0` was reported. Performing such a command on early
> linux versions resulted in this:
>
> Script started on Wed Feb 28 11:10:11 2001
> mke2fs /dev/loop0
> mke2fs 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09
> mke2fs: Device size reported to be zero. Invalid partition specified, or
> partition table wasn't reread after running fdisk, due to
> a modified partition being busy and in use. You may need to reboot
> to re-read your partition table.
>
> # exit
> exit
This was the report:
[on mke2fs]
This command hangs my system. It works for a 100K file, but it
hangs my system, if the file is 470M. It does not matter, if the
disk is SCSI or ide.
so you pretty much have to assume that he's losetup the files first.
How else could he state that it works for a 100k file, but not for
a 470m one?
BLKGETSIZE will return the device size, nothing unexpected here.
--
Jens Axboe
prev parent reply other threads:[~2001-02-28 16:24 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
2001-02-28 16:16 ` Richard B. Johnson
2001-02-28 16:23 ` Jens Axboe [this message]
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=20010228172345.K21518@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.