From: Mario Holbe <Mario.Holbe@TU-Ilmenau.DE>
To: "Piszcz, Justin Michael" <justin.piszcz@mitretek.org>
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
Andries Brouwer <aebr@win.tue.nl>,
linux-kernel@vger.kernel.org
Subject: Re: 2.4: "access beyond end of device" after ext2 mount
Date: Tue, 18 Jan 2005 15:02:03 +0100 [thread overview]
Message-ID: <20050118140203.GH2839@darkside.22.kls.lan> (raw)
In-Reply-To: <2E314DE03538984BA5634F12115B3A4E01BC42AE@email1.mitretek.org>
On Tue, Jan 18, 2005 at 08:42:08AM -0500, Piszcz, Justin Michael wrote:
> Normally, this problem associated with drives over 32GB or 127GB on a
> controller that cannot support it. It was not discussed here, I was
> wondering if that is the problem, if it is not, what type of Hard Drive
> is giving you these problems?
This does not depend on the type of the hard disk for sure.
root@darkside:/dev/shm# dd if=/dev/zero of=foo bs=1024 count=10001
10001+0 records in
10001+0 records out
10241024 bytes transferred in 0,062195 seconds (164659895 bytes/sec)
root@darkside:/dev/shm# losetup /dev/loop0 foo
loop: loaded (max 8 devices)
root@darkside:/dev/shm# mke2fs -b 4096 /dev/loop0
...
root@darkside:/dev/shm# blockdev --getbsz /dev/loop0
1024
root@darkside:/dev/shm# dd if=/dev/loop0 of=/dev/null
20002+0 records in
20002+0 records out
10241024 bytes transferred in 0,248255 seconds (41252031 bytes/sec)
root@darkside:/dev/shm# mount -o ro /dev/loop0 /mnt
root@darkside:/dev/shm# umount /dev/loop0
root@darkside:/dev/shm# blockdev --getbsz /dev/loop0
4096
root@darkside:/dev/shm# dd if=/dev/loop0 of=/dev/null
attempt to access beyond end of device
07:00: rw=0, want=10004, limit=10001
dd: reading `/dev/loop0': Input/output error
20000+0 records in
20000+0 records out
10240000 bytes transferred in 0,185949 seconds (55068833 bytes/sec)
Of course you could reproduce it much more simple without all
the ext2 stuff using blockdev --setbsz :)
Mario
--
() Ascii Ribbon Campaign
/\ Support plain text e-mail
next prev parent reply other threads:[~2005-01-18 14:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-18 13:42 2.4: "access beyond end of device" after ext2 mount Piszcz, Justin Michael
2005-01-18 14:02 ` Mario Holbe [this message]
2005-01-18 14:17 ` Sytse Wielinga
2005-01-18 15:20 ` Mario Holbe
2005-01-18 15:55 ` Sytse Wielinga
2005-01-18 16:12 ` Sytse Wielinga
[not found] <fa.f2nt105.94e81t@ifi.uio.no>
[not found] ` <fa.ihdogs4.bjglrq@ifi.uio.no>
2005-01-21 12:11 ` Bodo Eggert
-- strict thread matches above, loose matches on Subject: below --
2005-01-18 15:07 Piszcz, Justin Michael
2005-01-18 15:42 ` Mario Holbe
2005-01-18 14:24 Piszcz, Justin Michael
2005-01-18 15:03 ` Andries Brouwer
2005-01-18 15:29 ` Mario Holbe
2005-01-18 14:05 Piszcz, Justin Michael
2005-01-18 14:15 ` Mario Holbe
2005-01-15 23:35 Mario Holbe
2005-01-17 19:46 ` Marcelo Tosatti
2005-01-18 8:20 ` Mario Holbe
2005-01-18 10:55 ` Andries Brouwer
2005-01-18 8:45 ` Marcelo Tosatti
2005-01-18 12:15 ` Mario Holbe
2005-01-18 12:37 ` Andries Brouwer
2005-01-18 10:20 ` Marcelo Tosatti
2005-01-18 11:47 ` Mario Holbe
2005-01-18 12:39 ` Andries Brouwer
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=20050118140203.GH2839@darkside.22.kls.lan \
--to=mario.holbe@tu-ilmenau.de \
--cc=aebr@win.tue.nl \
--cc=justin.piszcz@mitretek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.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