A little nit-picking...
# echo check /sys/block/md0/md/sync_action
# cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid5] [raid4]
md1 : active raid1 sda7[1] hda7[0]
6253248 blocks [2/2] [UU]
md2 : active raid5 sdd1[2] sdc1[3] sdb1[1] hdc1[0] hdb1[4]
976783616
On Saturday May 27, [EMAIL PROTECTED] wrote:
On Sat, 27 May 2006, Neil Brown wrote:
Thanks. This narrows it down quite a bit... too much infact: I can
now say for sure that this cannot possible happen :-)
2/ The message.gz you sent earlier with the
echo t
On Fri, May 26, 2006 at 04:33:08PM +1000, Neil Brown wrote:
I am pleased to announce the availability of
mdadm version 2.5
hello,
i tried rebuilding mdadm 2.5 on current mandriva cooker, which uses
gcc-4.1.1, glibc-2.4 and dietlibc 0.29 and found the following issues
addressed by patches
On Sun, 28 May 2006, Luca Berra wrote:
- mdadm-2.5-rand.patch
Posix dictates rand() versus bsd random() function, and dietlibc
deprecated random(), so switch to srand()/rand() and make everybody
happy.
fwiw... lots of rand()s tend to suck... and RAND_MAX may not be large
enough for this
On Sun, May 28, 2006 at 10:08:19AM -0700, dean gaudet wrote:
On Sun, 28 May 2006, Luca Berra wrote:
- mdadm-2.5-rand.patch
Posix dictates rand() versus bsd random() function, and dietlibc
deprecated random(), so switch to srand()/rand() and make everybody
happy.
fwiw... lots of rand()s tend
On Sun, 28 May 2006, Luca Berra wrote:
dietlibc rand() and random() are the same function.
but random will throw a warning saying it is deprecated.
that's terribly obnoxious... it's never going to be deprecated, there are
only approximately a bazillion programs using random().
-dean
-
To
On Sunday May 28, [EMAIL PROTECTED] wrote:
On Fri, May 26, 2006 at 04:33:08PM +1000, Neil Brown wrote:
I am pleased to announce the availability of
mdadm version 2.5
hello,
i tried rebuilding mdadm 2.5 on current mandriva cooker, which uses
gcc-4.1.1, glibc-2.4 and dietlibc 0.29
On Sunday May 28, [EMAIL PROTECTED] wrote:
Hello Luca,
maybe you better add an install-static target.
you're right, that would be a cleaner approach. I've don so, and while
doing so added install-tcc, install-ulibc, install-klibc too.
And while I'm busy in the Makefile anyway I've made
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 same
On Friday May 26, [EMAIL PROTECTED] wrote:
I had no idea about this particular configuration requirement. None of
just to be clear: it's not a requirement. if you want the very nice
auto-assembling behavior, you need to designate the auto-assemblable
partitions. but you can assemble
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 Thu, 25 May 2006, Craig Hollabaugh wrote:
That did it! I set the partition FS Types from 'Linux' to 'Linux raid
autodetect' after my last re-sync completed. Manually stopped and
started the array. Things looked good, so I crossed my fingers
On Mon, May 29, 2006 at 12:08:25PM +1000, Neil Brown wrote:
On Sunday May 28, [EMAIL PROTECTED] wrote:
Thanks for the patches. They are greatly appreciated.
You're welcome
- mdadm-2.3.1-kernel-byteswap-include-fix.patch
reverts a change introduced with mdadm 2.3.1 for redhat compatibility
13 matches
Mail list logo
