From: Neil Brown <neilb@suse.de>
To: "Dâniel Fraga" <fragabr@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: pata_via with software raid1: "attempt to access beyond end of device"
Date: Fri, 20 Jul 2007 12:59:41 +1000 [thread overview]
Message-ID: <18080.9501.524388.160581@notabene.brown> (raw)
In-Reply-To: message from Daniel Fraga on Thursday July 19
On Thursday July 19, fragabr@gmail.com wrote:
> On Fri, 20 Jul 2007 12:14:31 +1000
> Neil Brown <neilb@suse.de> wrote:
>
> > What does
> > od -D -j 65536 -N 4 /dev/md1
> > show. This is the size the reiserfs thinks it is using. Multiply by
> > 4 and you should get 77642048 or maybe a little less. If you get
> > more, then reiserfs think the device is bigger than it is. If don't
> > then I have no idea what the problem is.
>
> The output is:
>
> 0200000 19410528
> 0200004
>
> so...
>
> 19410528 x 4 = 77642112
>
> The difference (77642048 - 77642112) is 64.
So reiserfs thinks the devices is 64K larger than it really is. I
wonder how that happened.
>
> Does it help? What could I do now? Thanks!
It helps that we know why you get these errors. It looks like you
should be able to fix it with resize_reiserfs.
Looking at the man page I have, you could
umount /whatever
resize_reiserfs -s -64K /dev/md1
mount /whatever
However I recommend reading the man page yourself, as this isn't the
sort of thing you want to get wrong.
NeilBrown
next prev parent reply other threads:[~2007-07-20 2:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-19 2:24 pata_via with software raid1: "attempt to access beyond end of device" Dâniel Fraga
2007-07-19 3:54 ` Neil Brown
2007-07-19 18:23 ` Dâniel Fraga
2007-07-20 2:14 ` Neil Brown
2007-07-20 2:32 ` Dâniel Fraga
2007-07-20 2:59 ` Neil Brown [this message]
2007-07-21 21:18 ` Dâniel Fraga
2007-07-30 19:01 ` Cry Regarder
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=18080.9501.524388.160581@notabene.brown \
--to=neilb@suse.de \
--cc=fragabr@gmail.com \
--cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).