From: Jari Ruusu <jari.ruusu@pp.inet.fi>
To: torvalds@transmeta.com
Cc: Andries.Brouwer@cwi.nl, axboe@suse.de,
linux-kernel@vger.kernel.org, R.E.Wolff@BitWizard.nl
Subject: Re: loop device broken in 2.4.6-pre5
Date: Tue, 26 Jun 2001 11:18:47 +0300 [thread overview]
Message-ID: <3B384567.BE3BE0EA@pp.inet.fi> (raw)
In-Reply-To: <UTC200106212258.AAA370096.aeb@vlet.cwi.nl> <3B334F39.E25548E0@pp.inet.fi>
This patch fixes the problem. Please consider applying.
--- linux-2.4.6-pre5/drivers/block/loop.c Sat Jun 23 07:52:39 2001
+++ linux/drivers/block/loop.c Tue Jun 26 09:21:47 2001
@@ -653,7 +653,7 @@
bs = 0;
if (blksize_size[MAJOR(lo_device)])
bs = blksize_size[MAJOR(lo_device)][MINOR(lo_device)];
- if (!bs)
+ if (!bs || S_ISREG(inode->i_mode))
bs = BLOCK_SIZE;
set_blocksize(dev, bs);
Jari Ruusu wrote:
> 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.
> >
> > The default block size of a loop device is that of the underlying device.
> > There was a kernel bug that was recently fixed, where the block size
> > of a file backed loop device could be essentially random.
> > So, earlier you happened to get blocksize 1024, and you had room for
> > 10 blocks of size 1024.
> > Now you have blocksize 4096, and you have room for 2 blocks of size 4096.
> > There are no fractional blocks at the end of a block device.
>
> Why can't we keep the default at 1024 regardless of what the block size of
> underlying device is. There are some situations where all of loop device
> must be accessed before it is mounted (at which point the block size is set
> to desired value).
Regards,
Jari Ruusu <jari.ruusu@pp.inet.fi>
next prev parent reply other threads:[~2001-06-26 8:21 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 [this message]
2001-06-25 16:31 ` Rogier Wolff
-- 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=3B384567.BE3BE0EA@pp.inet.fi \
--to=jari.ruusu@pp.inet.fi \
--cc=Andries.Brouwer@cwi.nl \
--cc=R.E.Wolff@BitWizard.nl \
--cc=axboe@suse.de \
--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