Re: mke2fs /dev/loop0
Jens Axboe (firstname.lastname@example.org)
Wed, 28 Feb 2001 17:23:45 +0100
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
This was the report:
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.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/