A: As of 18 Sept 1997, it is "2.0.30 + pre-9 2.0.31 + Werner Fink's swapping patch + the alpha RAID patch". As of November 1997, it is 2.0.31 + ... !?
A:/usr/include/linux¸¦/usr/src/linux/include/linuxÀ¸·Î ½Éº¼¸¯ ¸µÅ©¸¦ °É¾î¶ó.raid5.cµîÀÇ »õÆÄÀÏÀ» Á¦´ë·Î µÈ À§Ä¡·Î º¹»çÇ϶ó. ¶§¶§·Î ÆÐÄ¡ ¸í·É¾î´Â »õ·Î¿î ÆÄÀÏÀ» ¸¸µéÁö ¸øÇÑ´Ù. ÆÐÄ¡½Ã-f¿É¼ÇÀ» »ç¿ëÇØº¸¶ó.Make sure that
/usr/include/linuxis a symbolic link to/usr/src/linux/include/linux.Make sure that the new files
raid5.c, etc. have been copied to their correct locations. Sometimes the patch command will not create new files. Try the-fflag onpatch.
A: raidtools-0.42´Â ftp://ftp.inria.fr/INRIA/Projects/cristal/Xavier.Leroy ¾òÀ» ¼ö ÀÖ´Â linuxthreads-0.6À» ÇÊ¿ä·Î ÇÑ´Ù. ¶ÇÇÑ, glibc v2.0µµ »ç¿ëÇÑ´Ù.raidtools-0.42 requires linuxthreads-0.6 from: ftp://ftp.inria.fr/INRIA/Projects/cristal/Xavier.Leroy Alternately, use glibc v2.0.
mdrun -a /dev/md0: Invalid argument
A: ù¹øÂ° »ç¿ëÇϱâ Àü¿¡mkraid¸¦ »ç¿ëÇÏ¿© RAID¸¦ ÃʱâÈ ÇÏ¿©¾ß ÇÑ´Ù.Use
mkraidto initialize the RAID set prior to the first use.mkraidensures that the RAID array is initially in a consistent state by erasing the RAID partitions. In addition,mkraidwill create the RAID superblocks.
mdrun -a /dev/md0: Invalid argument
¼³Á¤Àº.
cat /proc/mdstat ¸¦ ÇÏ¸é ¾Æ·¡¿Í °°Àº ¸Þ½ÃÁö°¡ ³ª¿É´Ï´Ù.
Personalities :
read_ahead not set
md0 : inactive sda1 sdb1 6313482 blocks
md1 : inactive
md2 : inactive
md3 : inactive
mdrun -a ·Î ¿À·ù¸¦ Ãâ·ÂÇØº¸¸é..
/dev/md0: Invalid argument ÀÌ·± ¸Þ½ÃÁö°¡ ³ª¿É´Ï´Ù.A:lsmod(¶Ç´Âcat /proc/modules)·Î raid ¸ðµâÀÌ ·ÎµåµÇ¾ú´ÂÁö È®ÀÎÇØ¶ó. ·ÎµåµÇ¾îÀÖÁö ¾Ê´Ù¸é,modprobe raid1¶Ç´Âmodprobe raid5·Î È®½ÇÈ÷ ·Îµå½ÃÄѶó. ¶Ç´Â autoloader¸¦ »ç¿ëÇÑ´Ù¸é,/etc/conf.modules¿¡ ¾Æ·¡¿Í °°Àº ÁÙÀ» Ãß°¡½ÃÄѶó.alias md-personality-3 raid1 alias md-personality-4 raid5Try
lsmod(or, alternately,cat /proc/modules) to see if the raid modules are loaded. If they are not, you can load them explicitly with themodprobe raid1ormodprobe raid5command. Alternately, if you are using the autoloader, and expectedkerneldto load them and it didn't this is probably because your loader is missing the info to load the modules. Edit/etc/conf.modulesand add the following lines:
alias md-personality-3 raid1 alias md-personality-4 raid5
mdadd -a ÀÇ ½ÇÇàÁß /dev/md0: No such file or directory
¿Í °°Àº ¸Þ½ÃÁö°¡ ³ª¿Ô½À´Ï´Ù. Á¤¸» ¾îµð¿¡µµ /dev/md0 °¡ ¾ø½À´Ï´Ù.
À̰ÍÀ» ¾î¶»°Ô ÇØ¾ß ÇÒ±î¿ä?
A: raid-tools´Â ·çÆ®°¡make installÇßÀ» ¶§, ÀÌ ÀåÄ¡µéÀ» ¸¸µç´Ù. ¶ÇÇÑ, ¾Æ·¡¿Í °°ÀÌ ÇÒ ¼öµµ ÀÖ´Ù.cd /dev ./MAKEDEV mdThe raid-tools package will create these devices when you run
make installas root. Alternately, you can do the following:cd /dev ./MAKEDEV md
/dev/md0¿¡ RAID¸¦ ¸¸µç ÈÄ mount ½Ãµµ½Ã¿¡ ¾Æ·¡¿Í °°Àº ¿¡·¯°¡
³³´Ï´Ù. ¹«¾ùÀÌ ¹®Á¦ÀԴϱî?
mount: wrong fs type, bad option, bad superblock on /dev/md0,
or too many mounted file systems.
A: ¸¶¿îÆ® ÇϱâÀü¿¡ ÆÄÀϽýºÅÛÀ» ¸¸µé¾î¾ß ÇÑ´Ù.mke2fs¸¦ »ç¿ëÇ϶ó.You need to create a file system on
/dev/md0before you can mount it. Usemke2fs.
mkraid·Î RAID-1À» À§ÇØ °¢°¢ÀÇ ÆÄƼ¼ÇÀ» Áö¿ì´Â Áß.
ÄÜ¼Ö»ó¿¡ "Cannot allocate free page" ÀÌ·± ¿¡·¯°¡ ³ª°í, system log¿¡
"Unable to handle kernel paging request at virtual address ..." ÀÌ·± ¿¡·¯°¡ ³³´Ï´Ù.
Truxton Fulton wrote:
On my Linux 2.0.30 system, while doing amkraidfor a RAID-1 device, during the clearing of the two individual partitions, I got"Cannot allocate free page"errors appearing on the console, and"Unable to handle kernel paging request at virtual address ..."errors in the system log. At this time, the system became quite unusable, but it appears to recover after a while. The operation appears to have completed with no other errors, and I am successfully using my RAID-1 device. The errors are disconcerting though. Any ideas?
A: ±×°ÍÀº 2.0.30 kernelÀÇ ¾Ë·ÁÁø ¹ö±×ÀÌ´Ù. 2.0.31·Î ¼öÁ¤Çϰųª 2.0.29·Î µ¹¾Æ°¡¶ó.This was a well-known bug in the 2.0.30 kernels. It is fixed in the 2.0.31 kernel; alternately, fall back to 2.0.29.
mdadd µÈ ÀåÄ¡¸¦ mdrun ÇÏ·Á°í Çϸé,
¾Æ·¡¿Í °°Àº ¸Þ½ÃÁö°¡ ³ª¿É´Ï´Ù.
''invalid raid superblock magic''.
A:mkraid¸¦ ½ÇÇàÇ϶ó.Make sure that you've run the
mkraidpart of the install procedure.
/dev/md0À» »ç¿ëÇÏ´Â µ¿¾È, Ä¿³ÎÀº ¾Æ·¡¿Í °°Àº
¿¡·¯µéÀ» ½ñ¾Æ³À´Ï´Ù.
md0: device not running, giving up !
, I/O error...
Àü, °¡»ó device¿¡ Á¦ device¸¦ ¼º°øÀûÀ¸·Î Ãß°¡½ÃÄ×¾ú½À´Ï´Ù.
When I access /dev/md0, the kernel spits out a
lot of errors like md0: device not running, giving up !
and I/O error.... I've successfully added my devices to
the virtual device.
A: »ç¿ëÇϱâ À§Çؼ device´Â ½ÇÇàµÇ¾î¾ß ÇÑ´Ù.mdrun -px /dev/md0¸¦ »ç¿ëÇ϶ó. x´Â RAID levelÀÌ´Ù.To be usable, the device must be running. Use
mdrun -px /dev/md0where x is l for linear, 0 for RAID-0 or 1 for RAID-1, etc.
cat /proc/mdstat ·Î´Â ÃÑÅ©±â°¡ ³ª¿ÀÁö¸¸,
df ¸í·ÉÀ¸·Î´Â ù¹øÂ° µð½ºÅ©ÀÇ Å©±â¹Û¿¡ ¾È³ª¿É´Ï´Ù.
I've created a linear md-dev with 2 devices.
cat /proc/mdstat shows
the total size of the device, but df only shows the size of the first
physical device.
A: óÀ½ »ç¿ëÇϱâ Àü¿¡ ¹Ýµå½Ãmkfs¸¦ ½ÇÇà¾ß ÇÑ´Ù.You must
mkfsyour new md-dev before using it the first time, so that the filesystem will cover the whole device.
/etc/mdtab¸¦ ¼³Á¤Çϰí ,mdadd, mdrun,fsck
µîÀ» »ç¿ëÇØ, µÎ°³ÀÇ /dev/mdX ÆÄƼ¼ÇÀ» ¸¸µé¾ú½À´Ï´Ù.
reboot Çϱâ Àü±îÁö ¸ðµç °ÍÀÌ ±¦Âú¾Æ º¸¿´Áö¸¸, reboot ÇÒ¶§, µÎ ÆÄƼ¼Ç¿¡¼ ¾Æ·¡¿Í °°Àº fsck
°¡ ³µÀ¾´Ï´Ù. fsck.ext2: Attempt to read block from filesystem resulted in short
read while trying too open /dev/md0
¿Ö ±×·¸°í ¾î¶»°Ô °íÃÄ¾ß Çϳª¿ä?
I've set up /etc/mdtab using mdcreate, I've
mdadd'ed, mdrun and fsck'ed
my two /dev/mdX partitions. Everything looks
okay before a reboot. As soon as I reboot, I get an
fsck error on both partitions: fsck.ext2: Attempt to read block from filesystem resulted in short
read while trying too open /dev/md0. Why?! How do
I fix it?!
A: ºÎÆÃ ÀÛ¾÷½Ã RAID ÆÄƼ¼ÇµéÀºfsckÀÌÀü¿¡ ¹Ýµå½Ã ½ÃÀ۵Ǿî¾ß ÇÑ´Ù.fsck´Â/etc/rc.d/rc.S¶Ç´Â/etc/rc.d/rc.sysinit¿¡¼ ºÒ·ÁÁú °ÍÀÌ´Ù. ÀÌ ÆÄÀϵéÀÇfsck -AÀü¿¡mdadd -ar¸¦ Ãß°¡Çضó.
During the boot process, the RAID partitions must be started
before they can be fsck'ed. This must be done
in one of the boot scripts. For some distributions,
fsck is called from /etc/rc.d/rc.S, for others,
it is called from /etc/rc.d/rc.sysinit. Change this
file to mdadd -ar *before* fsck -A
is executed. Better yet, it is suggested that
ckraid be run if mdadd returns with an
error. How do do this is discussed in greater detail in
question 14 of the section ''Error Recovery''.
invalid raid superblock magic
A: ÀÌ ¹ö±×´Â ÇöÀç °íÃÄÁ³´Ù.(97³â 9¿ù) ÃÖ±ÙÀÇ raid¹öÁ®À» »ç¿ëÇØ¶ó.This bug is now fixed. (September 97) Make sure you have the latest raid code.
Warning: could not write 8 blocks in inode table starting at 2097175
A: À̰ÍÀºmke2fsÀÇ ¹®Á¦ °°´Ù. Àӽ÷Π¼Ò½º¿¡¼e2fsprogs-1.10/lib/ext2fs/llseek.cÆÄÀÏÀÇ Ã¹#ifdef HAVE_LLSEEKÀü¿¡#undef HAVE_LLSEEK¸¦ Ãß°¡ÇÑÈÄ mke2fs¸¦ ÀçÄÄÆÄÀÏÇØ¼ »ç¿ëÇ϶ó.This seems to be a problem with
mke2fs(November 97). A temporary work-around is to get the mke2fs code, and add#undef HAVE_LLSEEKtoe2fsprogs-1.10/lib/ext2fs/llseek.cjust before the first#ifdef HAVE_LLSEEKand recompile mke2fs.
ckraid °¡ /etc/mdtab ¸¦ ÀÐÁö ¸øÇÕ´Ï´Ù.
A:/etc/mdtab¾ÈÀÇ RAID-0 / linear RAID ¼³Á¤Àº ¾²ÀÌÁö ¾Ê°í ÀÖ°í, Á»´õ ÈÄ¿¡¾ß Áö¿ø µÉ°ÍÀÌ´Ù./etc/raid1.confµîÀÇ ¼³Á¤ÆÄÀϵéÀ» »ç¿ëÇ϶ó.The RAID0/linear configuration file format used in
/etc/mdtabis obsolete, although it will be supported for a while more. The current, up-to-date config files are currently named/etc/raid1.conf, etc.
raid1.o) °°Àº ¸ðµâµéÀÌ ÀÚµ¿À¸·Î ·ÎµåµÇÁö ¾Ê½À´Ï´Ù.
mdrun Àü¿¡ ¼öµ¿À¸·Î modprobe¸¦ ½ÇÇà½ÃÄÑ¾ß Çϴµ¥, ¾î¶»°Ô À̰ÍÀ» °íÃÄ¾ß ÇÒ±î¿ä?
A:/etc/conf.modules¿¡ ¾Æ·¡¿Í °°Àº ÁÙÀ» Ãß°¡Çضó.alias md-personality-3 raid1 alias md-personality-4 raid5To autoload the modules, we can add the following to
/etc/conf.modules:alias md-personality-3 raid1 alias md-personality-4 raid5
mdadd ÇÑ ÈÄ, mdrun -p5 /dev/md0
½Ãµµ ÇßÁö¸¸, ¾Æ·¡¿Í °°Àº ¿À·ù°¡ ³ª¿Ô½À´Ï´Ù.
/dev/md0: Invalid argument
A: software RAIDÀÇ ±âº»¼³Á¤ 8°³ÀÌ´Ù.linux/md.hÀÇ#define MAX_REAL=8¸¦ Å©°Ô ¹Ù²ÛÈÄ, Ä¿³ÎÀ» ÀçÄÄÆÄÀÏ Ç϶ó.The default configuration for software RAID is 8 real devices. Edit
linux/md.h, change#define MAX_REAL=8to a larger number, and rebuild the kernel.
I can't make md work with partitions on our
latest SPARCstation 5. I suspect that this has something
to do with disk-labels.
A: Sun ÀÇ µð½ºÅ© ¶óº§Àº ÆÄƼ¼ÇÀÇ Ã¹ 1K ¿¡ ÀÖ´Ù. RAID-1¿¡¼´Â ext2fs ÆÄƼ¼ÇÀÌ ¸ðµç ¶óº§À» ¹«½Ã ÇÒ °ÍÀ̱⠶§¹®¿¡ ¹®Á¦°¡ ¾øÁö¸¸, ´Ù¸¥ ·¹º§µé¿¡ °üÇØ¼´Â ¾ÆÁ÷ ÇØ°áµÇÁö ¾Ê¾Ò´Ù.Sun disk-labels sit in the first 1K of a partition. For RAID-1, the Sun disk-label is not an issue since
ext2fswill skip the label on every mirror. For other raid levels (0, linear and 4/5), this appears to be a problem; it has not yet (Dec 97) been addressed.