Re: raidreconf

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Feb 08, 2002 at 01:31:43PM +0200, Cajoline wrote:
> Oh duh! I'm sorry, here's the file.
...

...
I will SHRINK your old device /dev/md0 of 6863248 blocks
to a new device /dev/md0 of 6863240 blocks
using a block-size of 16 KB
Is this what you want? (yes/no): yes
Converting 6863248 block device to 6863240 block device
Allocated free block map for 3 disks
3 unique disks detected.
Working (|) [05491707/06863248] [###################################
] Out of Memory: Killed process 198 (exim).
Out of Memory: Killed process 252 (bash).
Out of Memory: Killed process 253 (bash).
Out of Memory: Killed process 339 (raidreconf).
Terminated
...

Ok - this is not a raidreconf problem - you are running a kernel with
a bad VM - the OOM killer kills raidreconf, and there's really nothing
raidreconf can do about it.

You will probably see "cp" killed too, if you copy enough data, or
"dd" if you dd a lot of data between partitions.

-- 
................................................................
:   jakob@unthought.net   : And I see the elder races,         :
:.........................: putrid forms of man                :
:   Jakob Østergaard      : See him rise and claim the earth,  :
:        OZ9ABN           : his downfall is at hand.           :
:.........................:............{Konkhra}...............:
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux