From: Thomas Themel <themel@iwoars.net>
To: linux-kernel@vger.kernel.org
Subject: Device-backed loop broken in 2.6.0-test2?
Date: Thu, 7 Aug 2003 00:40:22 +0200 [thread overview]
Message-ID: <20030806224022.GA3741@iwoars.net> (raw)
Hi,
it seems that device backed loopback is broken in the 2.6.0-test2 series.
I've noticed the error while testing cryptoloop, but it still appears
reliably when using plain loop without encryption.
I set up a loopback device on an IDE partition
losetup /dev/loop0 /dev/hda6
and create an ext3 filesystem on it. Then, when trying to fill it with
data, it works for a while until errors of the form
Buffer I/O error on device loop0, logical block 377367
Buffer I/O error on device loop0, logical block 377380
Buffer I/O error on device loop0, logical block 377419
Buffer I/O error on device loop0, logical block 378937
Buffer I/O error on device loop0, logical block 378983
Buffer I/O error on device loop0, logical block 380008
Buffer I/O error on device loop0, logical block 380009
start to appear in the kernel log. This does not affect the writes,
however, and only manifests later when the filesystem breaks or data in
files is corrupted.
ciao,
--
[*Thomas Themel*] I read what some of you folks here write and all I can
[extended contact] say is that I hope you are inside the fireballs when the
[info provided in] freedom fighters take out the Great Satan.
[*message header*] - Tim May on cypherpunks
next reply other threads:[~2003-08-06 22:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-06 22:40 Thomas Themel [this message]
2003-08-07 0:40 ` Device-backed loop broken in 2.6.0-test2? Andrew Morton
2003-08-07 7:23 ` Thomas Themel
2003-08-07 16:07 ` Valdis.Kletnieks
2003-08-07 16:24 ` Valdis.Kletnieks
2003-08-07 16:29 ` Andrew Morton
2003-08-09 20:48 ` cryptoloop data corruption (was Re: Device-backed loop broken in 2.6.0-test2?) Thomas Themel
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=20030806224022.GA3741@iwoars.net \
--to=themel@iwoars.net \
--cc=linux-kernel@vger.kernel.org \
/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