-----------------------------------------
답변자가 기본적으로 참고할 내용입니다.
- 배포판(옵션)    : 
- 커널버전(옵션)
  : 
- 데몬버전(예:apache
 1.3.27) : 
- 데몬설치유형(RPM/컴파일/기타)
 : 
-----------------------------------------
갑자기　어제．　다른　엔지니어가　실수로

움직이는　레드햇　９．０서버에서　

ｆｓｃｋ를　실시한　모양입니다．

그것도．　마운트　되어　있는　파티션을

아래와　같이　말이죠．


# fsck
fsck 1.32 (09-Nov-2002)
e2fsck 1.32 (09-Nov-2002)

check aborted.
e2fsck 1.32 (09-Nov-2002)
/dev/sda1 is mounted.

WARNING!!!  Running e2fsck on a mounted filesystem may cause
SEVERE filesystem damage.

Do you really want to continue (y/n)? yes

/boot: recovering journal
/boot: clean, 45/130560 files, 36080/522081 blocks
e2fsck 1.32 (09-Nov-2002)
/dev/sda6 is mounted.

WARNING!!!  Running e2fsck on a mounted filesystem may cause
SEVERE filesystem damage.

Do you really want to continue (y/n)? yes

/home: recovering journal

Group descriptors look bad... trying backup blocks...
fsck.ext3: Invalid argument while checking ext3 journal for /home
e2fsck 1.32 (09-Nov-2002)
/dev/sda3 is mounted.

WARNING!!!  Running e2fsck on a mounted filesystem may cause
SEVERE filesystem damage.

Do you really want to continue (y/n)? yes

/usr: recovering journal
fsck.ext3: Bad magic number in super-block while trying to re-open /usr
e2fsck: io manager magic bad!
e2fsck 1.32 (09-Nov-2002)
/dev/sda2 is mounted.

WARNING!!!  Running e2fsck on a mounted filesystem may cause
SEVERE filesystem damage.

Do you really want to continue (y/n)? yes

/var: recovering journal
fsck.ext3: Bad magic number in super-block while trying to re-open /var
e2fsck: io manager magic bad!


위　내용을　보면，　／ｖａｒ　랑　／ｈｏｍｅ　두개의　�
�티션에

문제가　발생한것　같아　보이는데요．


이후에　갑자기　유저들에게서　서버　접속이　안된다고　�
�서보니

／ｖａｒ，　／ｈｏｍｅ　umount
 된　상태였던　모양입니다．


그래서　그대로　ｒｅｂｏｏｔ을　한것　같은데，

제가　가서보니．　리부팅　후에　ｂｏｏｔ과정에서　파일�
�스템　

체크　부분에
Give root password for maintenance

(Type Ctrl-d to proceed with normal startup)

위와　같은　메세지가　나와서．root　패스워드로　로그인후�
��


(Repair filesystem) 1 #

상태에서　파티션　정보를　　확인해본　결과


# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/sda5             494M  102M  367M  22% /
/dev/sda1             494M   20M  450M   5% /boot
none                  252M     0  252M   0% /dev/shm
/dev/sda3             4.9G  1.5G  3.2G  32% /usr


# fdisk -l

Disk /dev/sda: 17.9 GB, 17968398336 bytes
255 heads, 63 sectors/track, 2184 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot    Start       End    Blocks   Id  System
/dev/sda1   *         1        65    522081   83  Linux
/dev/sda2            66       702   5116702+  83  Linux
/dev/sda3           703      1339   5116702+  83  Linux
/dev/sda4          1340      2184   6787462+   f  Win95 Ext'd (LBA)
/dev/sda5          1340      1404    522081   83  Linux
/dev/sda6          1405      2184   6265318+  83  Linux


# cat /proc/partitions
major minor  #blocks  name     rio rmerge rsect ruse wio wmerge wsect wuse runni
ng use aveq

   8     0   17547264 sda 1784 7980 27976 8360 594 1240 5922 63060 0 12350 71420
   8     1     522081 sda1 23 71 188 100 8 3 22 660 0 760 760
   8     2    5116702 sda2 19 58 196 100 0 0 0 0 0 100 100
   8     3    5116702 sda3 442 1068 11426 2360 152 222 2976 13090 0 5850 15450
   8     4          1 sda4 0 0 0 0 0 0 0 0 0 0 0
   8     5     522081 sda5 1282 6693 15950 5660 434 1015 2924 49310 0 9280 54970
   8     6    6265318 sda6 11 49 120 60 0 0 0 0 0 60 60

파티션은　다　살아　있더군요．



마운트를　했을때

# mount /dev/sda6 /home
mount: wrong fs type, bad option, bad superblock on /dev/sda6,
       or too many mounted file systems


ｆｓｃｋ를　했을때

# fsck.ext3 /dev/sda6
e2fsck 1.32 (09-Nov-2002)
Group descriptors look bad... trying backup blocks...
fsck.ext3: Invalid argument while checking ext3 journal for /home

어느것을　해도　콘솔에서　안돼서　어쩔수　없이　

ｆｓｔａｂ를　아래와　같이　수정후에


＊수정한　내용으　／ｈｏｍｅ을　코멘트　처리했습니다．


# more /etc/fstab
LABEL=/                 /                       ext3    defaults        1 1
LABEL=/boot             /boot                   ext3    defaults        1 2
none                    /dev/pts                devpts  gid=5,mode=620  0 0
#LABEL=/home             /home                   ext3    defaults        1 2
none                    /proc                   proc    defaults        0 0
none                    /dev/shm                tmpfs   defaults        0 0
LABEL=/usr              /usr                    ext3    defaults        1 2
LABEL=/var              /var                    ext3    defaults        1 2

어째든　위와　같이　조치후에　ｒｅｂｏｏｔ해서．

서버를　기동은　어떻게　했습니다．물론　무수한　에러　메
세지가　

나왔지만요．

그리고　원격지에서　ｓｓｈ를　통해　작업　할려고　

# /etc/init.d/sshd start
하니　／ｖａｒ　안에　필요한　폴더　및　파일이　없다고　
해서

강제로　만들었습니다．

# ls -al /var
total 5
drwxr-xr-x    5 root     root         1024 12月 19 20:52 .
drwxr-xr-x   21 root     root         1024 12月 20 19:15 ..
drwxr-xr-x    2 root     root         1024 12月 19 20:52 empty
drwxr-xr-x    3 root     root         1024 12月 19 20:16 lib
drwxr-xr-x    3 root     root         1024 12月 19 20:52 lock

기존에　／ｖａｒ　파티션을　별도로　나누어서　사용했는데

／ｖａｒ　파티션도　마운트　안되더군요．．


어째든　제가　필요한　테이타는　／ｈｏｍｅ　안에　테이타
만　중요해서말이죠．


ｅ２ｆｓｃｋ를　실행했을경우

# e2fsck /dev/sda6
e2fsck 1.32 (09-Nov-2002)
Group descriptors look bad... trying backup blocks...
e2fsck: Invalid argument while checking ext3 journal for /home

# e2fsck /dev/sda2
e2fsck 1.32 (09-Nov-2002)
/var: clean, 1384/640000 files, 25001/1279175 blocks

＊／ｖａｒ는　괜찮은것　같은데．마운트　해도　아무　테이
타가　없네요


# mount /dev/sda2 /var1
# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/sda5             494M  102M  367M  22% /
/dev/sda1             494M   20M  450M   5% /boot
none                  252M     0  252M   0% /dev/shm
/dev/sda3             4.9G  1.5G  3.2G  32% /usr
/dev/sda2             4.9G   20M  4.6G   1% /var1


# ls -al /var1/
total 29
drwxr-xr-x    3 root     root         4096 12月 19 18:43 .
drwxr-xr-x   21 root     root         1024 12月 20 19:15 ..
drwx------    8 root     root        24576 12月 19 18:43 lost+found





슈퍼　블록으로　복구　테스트

# e2fsck -b 8193 /dev/sda6
e2fsck 1.32 (09-Nov-2002)
e2fsck: Bad magic number in super-block while trying to open /dev/sda6

The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>

배트불록　체크

# e2fsck -cv  /dev/sda6
e2fsck 1.32 (09-Nov-2002)
Group descriptors look bad... trying backup blocks...
e2fsck: Invalid argument while checking ext3 journal for /home

강제복구　
# e2fsck -f  /dev/sda6
e2fsck 1.32 (09-Nov-2002)
Group descriptors look bad... trying backup blocks...
e2fsck: Invalid argument while checking ext3 journal for /home



제가　한것은　여기　까지　인데요．．다　안되더군요．

혹　　복구　가능한　방법이나　제가　놓치것이　있으면　�
�씀　부탁드립니다．

／ｖａｒ　어떻게　될것　같아　보이는데　잘　안되네요．�
�．

산이님께　여쭈어　보고　안되면　업체쪽으로　알아볼까　하
는데요．



하나　더　여쭈어　볼께요．

현재　아래와　같은　파일이　서버에　있는데　삭제가　안�
�네요．

 ls -al
合計 282408
-rw-r--r--    1 root     root            0  5月 15  2006 ??暼???????-

rw-r--r--    1 root     root          191  2月 22  2006 -v

# rm -rf "-v"

이렇게　해도　삭제　안되고　？？？형태로　생긴파일은　삭
제해볼려고　해도


# ls  -al 　?*　
형태로　먼저　확인해보면　？　자체가　임이의문자　하나�
�　인식해버리니　다른　파일까지　삭제　되버리니．．


어떤　좋은　방법이　있을까요？


긴　내용　읽어　주셨서　감사합니다．