From: R.E.Wolff@BitWizard.nl (Rogier Wolff)
To: Andries.Brouwer@cwi.nl
Cc: jari.ruusu@pp.inet.fi, torvalds@transmeta.com, axboe@suse.de,
linux-kernel@vger.kernel.org
Subject: Re: loop device broken in 2.4.6-pre5
Date: Mon, 25 Jun 2001 18:31:07 +0200 (MEST) [thread overview]
Message-ID: <200106251631.SAA09431@cave.bitwizard.nl> (raw)
In-Reply-To: <UTC200106212258.AAA370096.aeb@vlet.cwi.nl> from "Andries.Brouwer@cwi.nl" at "Jun 22, 2001 00:58:53 am"
Andries.Brouwer@cwi.nl wrote:
> From: Jari Ruusu <jari.ruusu@pp.inet.fi>
>
> File backed loop device on 4k block size ext2 filesystem:
>
> # dd if=/dev/zero of=file1 bs=1024 count=10
> 10+0 records in
> 10+0 records out
> # losetup /dev/loop0 file1
> # dd if=/dev/zero of=/dev/loop0 bs=1024 count=10 conv=notrunc
> dd: /dev/loop0: No space left on device
> 9+0 records in
> 8+0 records out
> # tune2fs -l /dev/hda1 2>&1| grep "Block size"
> Block size: 4096
> # uname -a
> Linux debian 2.4.6-pre5 #1 Thu Jun 21 14:27:25 EEST 2001 i686 unknown
>
> Stock 2.4.5 and 2.4.5-ac15 don't have this problem.
>
> I am not sure there is an error here.
How about:
dd if=/dev/hda1 of=disk.img bs=1k
mount disk.img /mnt/d1 -o loop
If the filesystem on hda1 happens to use the last 2k of the partition,
and the partition size is 2k mod 4k, then I get a non-working disk.img
if I don't pad the disk.img file with another 2k. And then I might
trip up the "how big is this partition" code in the fs-driver....
Roger.
--
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2137555 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
* There are old pilots, and there are bold pilots.
* There are also old, bald pilots.
next prev parent reply other threads:[~2001-06-25 16:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-21 22:58 loop device broken in 2.4.6-pre5 Andries.Brouwer
2001-06-22 13:59 ` Jari Ruusu
2001-06-26 8:18 ` Jari Ruusu
2001-06-25 16:31 ` Rogier Wolff [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-06-26 13:31 Andries.Brouwer
2001-06-26 10:41 Andries.Brouwer
2001-06-26 10:52 ` Rogier Wolff
2001-06-26 17:59 ` Jari Ruusu
2001-06-26 19:14 ` Anton Altaparmakov
2001-06-27 11:54 ` Jari Ruusu
2001-06-21 16:43 Jari Ruusu
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=200106251631.SAA09431@cave.bitwizard.nl \
--to=r.e.wolff@bitwizard.nl \
--cc=Andries.Brouwer@cwi.nl \
--cc=axboe@suse.de \
--cc=jari.ruusu@pp.inet.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox