From: Sandro Dentella <sandro.dentella@tin.it>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: Sandro Dentella <sandro.dentella@tin.it>, linux-raid@vger.kernel.org
Subject: Re: mdadm: hot add failed ... lun0/part6: No space left on device
Date: Tue, 3 Feb 2004 09:01:04 +0100 [thread overview]
Message-ID: <20040203080104.GA10152@e-den.it> (raw)
In-Reply-To: <16411.34391.455191.631246@notabene.cse.unsw.edu.au>
On Sat, Jan 31, 2004 at 09:41:27PM +1100, Neil Brown wrote:
> > # mdadm /dev/md1 --add /dev/ide/host0/bus1/target0/lun0/part6
> >
> > but I get:
> >
> > mdadm: hot add failed for /dev/ide/host0/bus1/target0/lun0/part6: No space left on device
> It means, as you guess lower down, that the partition you have
> provided appears to be too small to be used in the given array.
>
> This error should cause a message to appear in the kernel logs
> something like
>
> md1: disk size XXX blocks < array size YYY
>
> You might finding it by
> dmesg | grep 'disk size'
>
> or looking in some file in /var/log (depending on which distribution
> you use. Debian puts it in /var/log/kern.log).
It's a pity the system was running on a rescue CD so when I had to reboot
(the client really needed to have it up soon) I lost the messages. I can
tell that I bypassed the problem swapping the position of the two HD (hda
and hdc). At that point both where seen in LBA mode and the partition could
be added... I that any usefull to help understand? Is there anything I
could/should have been done to avoid this behaviour?
Why hdc is so often seen not in LBA mode (BIOS set up correctly) until you
force it w/ fdisk while hda is always right?
Thanks for your help
sandro
*:-)
--
Sandro Dentella *:-)
e-mail: sandro.dentella@tin.it
http://www.tksql.org TkSQL Home page - My GPL work
prev parent reply other threads:[~2004-02-03 8:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-30 12:32 mdadm: hot add failed ... lun0/part6: No space left on device Sandro Dentella
2004-01-31 10:41 ` Neil Brown
2004-02-03 8:01 ` Sandro Dentella [this message]
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=20040203080104.GA10152@e-den.it \
--to=sandro.dentella@tin.it \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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).