From: Arctic Paintball Oy <aps@sgic.fi>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] 2.6.9-r1 kernel bug?
Date: Wed, 8 Dec 2004 10:34:06 +0200 (EET) [thread overview]
Message-ID: <Pine.OSF.4.21.0412081025170.27807-100000@Platon.sgic.fi> (raw)
Couldnt find anything on this googling around. Am I missing something or
is this a bug?
How is it possible to try to read beyond the end of device on the loop
device? Or should i use dd? Is this a bug or are the files damaged. I cant
check the old contents any longer so md5sum is not an option.
To bad this packaging is totaly idiotic (i mean iso image of bin/cue
;-) ). I was trying to make it a little easier to use without double
packaging
dmesg output:
attempt to access beyond end of device
loop0: rw=0, want=790536, limit=790528
Buffer I/O error on device loop0, logical block 197633
umount temp/
mount image.iso temp/ -t iso9660 -o loop
cp temp/* .
cp: reading `temp/image.bin': Input/output error
cp: reading `temp/image.cue': Input/output error
TIA
Christian
--
gentoo-user@gentoo.org mailing list
next reply other threads:[~2004-12-08 8:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-08 8:34 Arctic Paintball Oy [this message]
2004-12-08 10:45 ` [gentoo-user] 2.6.9-r1 kernel bug? Nicolai Guba
2004-12-08 11:43 ` Arctic Paintball Oy
2004-12-08 14:50 ` Billy
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=Pine.OSF.4.21.0412081025170.27807-100000@Platon.sgic.fi \
--to=aps@sgic.fi \
--cc=gentoo-user@lists.gentoo.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