Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Reboot is definately not helping... AND to make matters more complicated - i got it backwards. We went from a 0.8 & a 1.0TB (1.8TB) drives Raided togther to 1.0 & 1.4TB (2.4TB) drives raided together - so we're actually going LARGER - not smaller. (still the same crash though). D> ----- Original Message ----- From: "Lars Ellenberg" <Lars.Ellenberg at linbit.com> To: <drbd-user at lists.linbit.com> Sent: Tuesday, April 19, 2005 9:28 AM Subject: Re: [DRBD-user] Resized the Raid.... >/ 2005-04-19 08:46:31 -0500 > \ David A. Smith: >> Ack.... Is there ANYWAY to clean this out? - i have no data i want to >> save >> - but i have a customer waiting on this getting back up and running. > > for now: > see if a reboot helps, > sometimes allocating large amount of memory is easier just after reboot. > (it will BUG again, though, if it can not allocate enough). > > also try the vmalloc=something boot parameter. though, on a power mac > (64bit arch), there should be no reason for this. *scratch head* > If at all, I had expected this on a 32bit x86 arch... > > Lars > _______________________________________________ > drbd-user mailing list > drbd-user at lists.linbit.com > http://lists.linbit.com/mailman/listinfo/drbd-user >