From: PFC <lists@peufeu.com>
To: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: attempt to access beyond end of device
Date: Thu, 19 Jan 2006 21:39:27 +0100 [thread overview]
Message-ID: <op.s3m7n1pucigqcu@apollo13> (raw)
In-Reply-To: <op.s3mjqms2i22er4@xray.bmc.uu.se>
OK, I was a bit stupid...
I changed a drive today, so I rebuilt a software RAID1.
I have a RAID1 in degraded mode (1 out of 2 drives), and I added a new
partition to it. When I say I was stupid, I mean the partition I added was
a tiny little bit smaller than what it should have been.
md happily added it, synced, then at the very end :
Jan 19 21:33:27 apollo13 attempt to access beyond end of device
Jan 19 21:33:27 apollo13 sda7: rw=1, want=12498560, limit=12498507
Jan 19 21:33:27 apollo13 raid1: Disk failure on sda7, disabling device.
Jan 19 21:33:27 apollo13 Operation continuing on 1 devices
Of course, "attempt to access beyond end of device", I made the device
too small. Duh.
No problem, I'll just fix my partition, but a warning message on the
mdadm --add would have avoided losing time doing the sync, and at the end,
a few seconds of "WTF ? it failed ? ah, ok..."
Have a nice day !
mdadm --version
mdadm - v2.1 - 12 September 2005
next prev parent reply other threads:[~2006-01-19 20:39 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-19 12:02 Handling of read errors in raid6 Filipe Maia
2006-01-19 20:39 ` PFC [this message]
2006-01-19 21:29 ` raid reconstruction speed PFC
2006-01-19 22:10 ` Mike Hardy
2006-01-19 23:27 ` Mark Hahn
2006-01-19 22:27 ` Neil Brown
2006-01-19 22:37 ` PFC
-- strict thread matches above, loose matches on Subject: below --
2014-03-24 7:13 attempt to access beyond end of device Piotr Szymaniak
2014-03-24 7:37 ` Vyacheslav Dubeyko
2014-03-24 20:49 ` Piotr Szymaniak
2014-03-25 9:18 ` Vyacheslav Dubeyko
2014-03-27 12:39 ` Piotr Szymaniak
2014-03-29 14:49 ` Vyacheslav Dubeyko
2014-03-24 22:31 ` Piotr Szymaniak
2010-04-26 20:20 Re: Attempt to Access Beyond End of Device willis
2010-04-26 20:54 ` Eric Sandeen
2007-09-10 13:59 Federico Sevilla III
2007-09-10 14:44 ` Justin Piszcz
2007-09-10 14:59 ` Federico Sevilla III
2007-09-10 15:45 ` Justin Piszcz
2007-09-10 15:51 ` Federico Sevilla III
2007-09-10 15:47 ` Eric Sandeen
2007-09-10 15:54 ` Federico Sevilla III
2007-09-10 16:28 ` Eric Sandeen
[not found] ` <cc7060690709111208u3e0842f9rd6edff16539b8a28@mail.gmail.com>
2007-09-12 5:17 ` Federico Sevilla III
2006-12-05 14:01 attempt to access beyond end of device Koen Vereeken
2004-04-13 10:03 Luca Ferrari
2004-04-13 10:41 ` Thomas Steudten
2004-04-13 11:08 ` Luca Ferrari
2004-04-13 11:20 ` Thomas Steudten
2004-04-13 11:45 ` Luca Ferrari
2004-04-13 12:44 ` Thomas Steudten
2004-04-13 12:53 ` Luca Ferrari
2002-12-06 5:21 Justin Pryzby
2002-12-05 18:54 Justin Pryzby
2000-12-07 15:56 Jan Niehusmann
2000-12-07 16:34 ` Andries Brouwer
2000-12-07 17:10 ` John Kennedy
2000-11-24 9:02 Janek
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=op.s3m7n1pucigqcu@apollo13 \
--to=lists@peufeu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.