From: Mario Holbe <Mario.Holbe@TU-Ilmenau.DE>
To: Andries Brouwer <aebr@win.tue.nl>
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
linux-kernel@vger.kernel.org
Subject: Re: 2.4: "access beyond end of device" after ext2 mount
Date: Tue, 18 Jan 2005 12:47:01 +0100 [thread overview]
Message-ID: <20050118114701.GD2839@darkside.22.kls.lan> (raw)
In-Reply-To: <20050118105547.GD8747@pclin040.win.tue.nl>
On Tue, Jan 18, 2005 at 11:55:47AM +0100, Andries Brouwer wrote:
> I suppose that what happens is the following:
> mounting sets the blocksize to 4096.
> After reading 9992360 sectors, reading the next block means reading
> the next 8 sectors and that fails because only 6 sectors are left.
> Test that this is what happens using blockdev --getbsz.
Yes! This was the command I was looking for ;)
root@darkside:~# blockdev --getbsz /dev/hdg7
4096
root@darkside:~# blockdev --getbsz /dev/hdg6
1024
root@darkside:~# mount -t ext3 -o ro /dev/hdg6 /mnt
root@darkside:~# umount /dev/hdg6
root@darkside:~# blockdev --getbsz /dev/hdg6
4096
> If you want to restore the device to full size, use
> blockdev --setbsz 512.
Does that in any way hurt, if a filesystem is just mounted?
I mean, what would happen, if I mount /dev/hdg7 and then
set the block size back to 1024? Would that perhaps corrupt
my filesystem or something like that?
Mario
--
<jv> Oh well, config
<jv> one actually wonders what force in the universe is holding it
<jv> and makes it working
<Beeth> chances and accidents :)
next prev parent reply other threads:[~2005-01-18 11:48 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-15 23:35 2.4: "access beyond end of device" after ext2 mount 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 [this message]
2005-01-18 12:39 ` Andries Brouwer
-- strict thread matches above, loose matches on Subject: below --
2005-01-18 13:42 Piszcz, Justin Michael
2005-01-18 14:02 ` Mario Holbe
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
2005-01-18 14:05 Piszcz, Justin Michael
2005-01-18 14:15 ` 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 15:07 Piszcz, Justin Michael
2005-01-18 15:42 ` Mario Holbe
[not found] <fa.f2nt105.94e81t@ifi.uio.no>
[not found] ` <fa.ihdogs4.bjglrq@ifi.uio.no>
2005-01-21 12:11 ` Bodo Eggert
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=20050118114701.GD2839@darkside.22.kls.lan \
--to=mario.holbe@tu-ilmenau.de \
--cc=aebr@win.tue.nl \
--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