public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andries.Brouwer@cwi.nl
To: jari.ruusu@pp.inet.fi, torvalds@transmeta.com
Cc: axboe@suse.de, linux-kernel@vger.kernel.org
Subject: Re: loop device broken in 2.4.6-pre5
Date: Fri, 22 Jun 2001 00:58:53 +0200 (MET DST)	[thread overview]
Message-ID: <UTC200106212258.AAA370096.aeb@vlet.cwi.nl> (raw)

    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.

Andries

             reply	other threads:[~2001-06-21 22:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-21 22:58 Andries.Brouwer [this message]
2001-06-22 13:59 ` loop device broken in 2.4.6-pre5 Jari Ruusu
2001-06-26  8:18   ` Jari Ruusu
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=UTC200106212258.AAA370096.aeb@vlet.cwi.nl \
    --to=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