Luca Berra wrote:
On Tue, May 30, 2006 at 01:10:24PM -0400, Bill Davidsen wrote:
2) deprecate the "DEVICE" keyword issuing a warning when it is
found in
the configuration file
Not sure I'm so keen on that, at least not in the near term.
Let's not start warning and depreciating powerful fe
On Tue, May 30, 2006 at 01:10:24PM -0400, Bill Davidsen wrote:
2) deprecate the "DEVICE" keyword issuing a warning when it is found in
the configuration file
Not sure I'm so keen on that, at least not in the near term.
Let's not start warning and depreciating powerful features because they
ca
Neil Brown wrote:
On Friday May 26, [EMAIL PROTECTED] wrote:
On Tue, May 23, 2006 at 08:39:26AM +1000, Neil Brown wrote:
Presumably you have a 'DEVICE' line in mdadm.conf too? What is it.
My first guess is that it isn't listing /dev/sdd? somehow.
Neil,
i am seeing a lot of peo
On Mon, May 29, 2006 at 12:38:25PM +0400, Michael Tokarev wrote:
Neil Brown wrote:
On Friday May 26, [EMAIL PROTECTED] wrote:
I'd suggest the following.
"All the other devices" are included or excluded from the list of devices
to consider based on the last component in the DEVICE line. Ie. if
Neil Brown wrote:
> On Friday May 26, [EMAIL PROTECTED] wrote:
[]
> If we assume there is a list of devices provided by a (possibly
> default) 'DEVICE' line, then
>
> DEVICEFILTER !pattern1 !pattern2 pattern3 pattern4
>
> could mean that any device in that list which matches pattern 1 or 2
> i
On Mon, May 29, 2006 at 02:21:09PM +1000, Neil Brown wrote:
3) introduce "DEVICEFILTER" or similar keyword with the same meaning at
the actual "DEVICE" keyboard
If it has the same meaning, why not leave it called 'DEVICE'???
the idea was to warn people that write
DEVICE /dev/sda1 /dev/sdb1 /
On Friday May 26, [EMAIL PROTECTED] wrote:
> On Tue, May 23, 2006 at 08:39:26AM +1000, Neil Brown wrote:
> >Presumably you have a 'DEVICE' line in mdadm.conf too? What is it.
> >My first guess is that it isn't listing /dev/sdd? somehow.
>
> Neil,
> i am seeing a lot of people that fall in this sa
On Fri, May 26, 2006 at 09:53:08AM +0200, Luca Berra wrote:
On Tue, May 23, 2006 at 08:39:26AM +1000, Neil Brown wrote:
Presumably you have a 'DEVICE' line in mdadm.conf too? What is it.
My first guess is that it isn't listing /dev/sdd? somehow.
Neil,
i am seeing a lot of people that fall in
On Tue, May 23, 2006 at 08:39:26AM +1000, Neil Brown wrote:
Presumably you have a 'DEVICE' line in mdadm.conf too? What is it.
My first guess is that it isn't listing /dev/sdd? somehow.
Neil,
i am seeing a lot of people that fall in this same error, and i would
propose a way of avoiding this p
On 24 May 2006, Florian Dazinger uttered the following:
> Neil Brown wrote:
>> Presumably you have a 'DEVICE' line in mdadm.conf too? What is it.
>> My first guess is that it isn't listing /dev/sdd? somehow.
>> Otherwise, can you add a '-v' to the mdadm command that assembles the
>> array, and cap
Neil Brown wrote:
Presumably you have a 'DEVICE' line in mdadm.conf too? What is it.
My first guess is that it isn't listing /dev/sdd? somehow.
Otherwise, can you add a '-v' to the mdadm command that assembles the
array, and capture the output. That might be helpful.
NeilBrown
stupid me! I h
On Monday May 22, [EMAIL PROTECTED] wrote:
> hi list,
> I read somewhere that it would be better not to rely on the
> autodetect-mechanism in the kernel at boot time, but rather to set up
> /etc/mdadm.conf accordingly and boot with raid=noautodetect. Well, I
> tried that :)
>
> I set up /etc/md
hi list,
I read somewhere that it would be better not to rely on the
autodetect-mechanism in the kernel at boot time, but rather to set up
/etc/mdadm.conf accordingly and boot with raid=noautodetect. Well, I
tried that :)
I set up /etc/mdadm.conf for my 2 raid5 arrays:
snip
# mount
13 matches
Mail list logo
