作者 主題: 有關bad block  (閱讀 3435 次)

0 會員 與 1 訪客 正在閱讀本文。

uck

  • 活潑的大學生
  • ***
  • 文章數: 224
    • 檢視個人資料
有關bad block
« 於: 2006-08-20 22:59 »
請教各位大大:

環境: RHEL3 32bit + SAMBA3

目錄裡有10幾萬個小檔案. 每個檔案大約3~4kb



請教各位學長有無遇過 下達 ll 指令會出現下列 error訊息, 但下達ls則不會有任何錯誤訊息.

在目錄  data_1裡執行 #ll  會出現以下訊息. 但 ls 則不會.
ls: file1: Input/output error
ls: file2: Input/output error
ls: file3: Input/output error
ls: file4: Input/output error
ls: file5: Input/output error
ls: file6: Input/output error


去查詢log 發現:

Aug 17 18:28:57 fileserver kernel: EXT3-fs error (device sd(8,19)): ext3_xattr_get: inode 163841: bad block 328198
Aug 17 18:28:57 fileserver kernel: EXT3-fs error (device sd(8,19)): ext3_xattr_get: inode 180225: bad block 328198
Aug 17 18:29:02 fileserver kernel: EXT3-fs error (device sd(8,19)): ext3_xattr_get: inode 163842: bad block 328199
Aug 17 18:29:02 fileserver kernel: EXT3-fs error (device sd(8,19)): ext3_xattr_get: inode 163843: bad block 328199
Aug 17 18:29:02 fileserver kernel: EXT3-fs error (device sd(8,19)): ext3_xattr_get: inode 163844: bad block 328199
Aug 17 18:29:02 fileserver kernel: EXT3-fs error (device sd(8,19)): ext3_xattr_get: inode 163845: bad block 328199
Aug 17 18:29:02 fileserver kernel: EXT3-fs error (device sd(8,19)): ext3_xattr_get: inode 163846: bad block 328199
Aug 17 18:29:02 fileserver kernel: EXT3-fs error (device sd(8,19)): ext3_xattr_get: inode 163847: bad block 328199
Aug 17 18:29:02 fileserver kernel: EXT3-fs error (device sd(8,19)): ext3_xattr_get: inode 163848: bad block 328199
Aug 17 18:29:02 fileserver kernel: EXT3-fs error (device sd(8,19)): ext3_xattr_get: inode 163849: bad block 328199
Aug 17 18:29:02 fileserver kernel: EXT3-fs error (device sd(8,19)): ext3_xattr_get: inode 163850: bad block 328199
Aug 17 18:29:02 fileserver kernel: EXT3-fs error (device sd(8,19)): ext3_xattr_get: inode 163851: bad block 328199
Aug 17 18:29:02 fileserver kernel: EXT3-fs error (device sd(8,19)): ext3_xattr_get: inode 163852: bad block 328199
Aug 17 18:29:02 fileserver kernel: EXT3-fs error (device sd(8,19)): ext3_xattr_get: inode 163853: bad block 328199
Aug 17 18:29:02 fileserver kernel: EXT3-fs error (device sd(8,19)): ext3_xattr_get: inode 163854: bad block 328199
Aug 17 18:29:02 fileserver kernel: EXT3-fs error (device sd(8,19)): ext3_xattr_get: inode 163855: bad block 328199
Aug 17 18:29:02 fileserver kernel: EXT3-fs error (device sd(8,19)): ext3_xattr_get: inode 163856: bad block 328227
Aug 17 18:29:02 fileserver kernel: EXT3-fs error (device sd(8,19)): ext3_xattr_get: inode 163857: bad block 328227
Aug 17 18:29:02 fileserver kernel: EXT3-fs error (device sd(8,19)): ext3_xattr_get: inode 163858: bad block 328227
Aug 17 18:29:02 fileserver kernel: EXT3-fs error (device sd(8,19)): ext3_xattr_get: inode 163859: bad block 328227
Aug 17 18:29:02 fileserver kernel: EXT3-fs error (device sd(8,19)): ext3_xattr_get: inode 163860: bad block 328227
Aug 17 18:29:02 fileserver kernel: EXT3-fs error (device sd(8,19)): ext3_xattr_get: inode 163861: bad block 328227
Aug 17 18:29:02 fileserver kernel: EXT3-fs error (device sd(8,19)): ext3_xattr_get: inode 163862: bad block 328227
Aug 17 18:29:02 fileserver kernel: EXT3-fs error (device sd(8,19)): ext3_xattr_get: inode 163863: bad block 328227
Aug 17 18:29:02 fileserver kernel: EXT3-fs error (device sd(8,19)): ext3_xattr_get: inode 163864: bad block 328227
Aug 17 18:29:02 fileserver kernel: EXT3-fs error (device sd(8,19)): ext3_xattr_get: inode 163865: bad block 328227
Aug 17 18:29:02 fileserver kernel: EXT3-fs error (device sd(8,19)): ext3_xattr_get: inode 163866: bad block 328247
Aug 17 18:29:02 fileserver kernel: EXT3-fs error (device sd(8,19)): ext3_xattr_get: inode 163867: bad block 328247
Aug 17 18:29:02 fileserver kernel: EXT3-fs error (device sd(8,19)): ext3_xattr_get: inode 163868: bad block 328247
Aug 17 18:29:02 fileserver kernel: EXT3-fs error (device sd(8,19)): ext3_xattr_get: inode 163869: bad block 328247
Aug 17 18:29:02 fileserver kernel: EXT3-fs error (device sd(8,19)): ext3_xattr_get: inode 163870: bad block 328247
Aug 17 18:29:02 fileserver kernel: EXT3-fs error (device sd(8,19)): ext3_xattr_get: inode 163871: bad block 328247
Aug 17 18:29:02 fileserver kernel: EXT3-fs error (device sd(8,19)): ext3_xattr_get: inode 163872: bad block 328247



也嘗試在目錄裡 #touck aaa    make 一個新的空檔:
不過出現 :  touch: creating `aaa': Input/output error

發現目錄不可以有檔案再寫入. 但讀取檔案則是可以的. (上述壞掉的檔案就不能讀了)

也使用過 dumpe2fs :

[root@fileserver /]# dumpe2fs /dev/sdb3
dumpe2fs 1.32 (09-Nov-2002)
Filesystem volume name:   <none>
Last mounted on:          <not available>
Filesystem UUID:          bc5c3e3e-2414-4a2a-b7ca-50c2b4742506
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr filetype needs_recovery sparse_super
Default mount options:    (none)
Filesystem state:         clean with errors
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              266846208
Block count:              533691348
Reserved block count:     26684567
Free blocks:              459672166
Free inodes:              265363645
First block:              0
Block size:               4096
Fragment size:            4096
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         16384
Inode blocks per group:   512
Filesystem created:       Wed Jun 14 16:18:27 2006
Last mount time:          Thu Aug 17 15:30:03 2006
Last write time:          Sun Aug 20 12:09:54 2006
Mount count:              93
Maximum mount count:      34
Last checked:             Wed Jun 14 16:18:27 2006
Check interval:           15552000 (6 months)
Next check after:         Mon Dec 11 16:18:27 2006
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:               128
Journal UUID:             <none>
Journal inode:            8
Journal device:           0x0000
First orphan inode:       0
 


請教各位學長,這裡看起來是有bad block出現. /dev/sdb3 是一個LUN.  Storage並沒有秀出任何錯誤. 請教是否有其它的方法可以救這個LUN. 謝謝.

aaronosos

  • 懷疑的國中生
  • **
  • 文章數: 43
    • 檢視個人資料
有關bad block
« 回覆 #1 於: 2006-08-21 15:09 »
試試這指令看看
e2fsck -b 8193 /dev/sdb3

uck

  • 活潑的大學生
  • ***
  • 文章數: 224
    • 檢視個人資料
有關bad block
« 回覆 #2 於: 2006-08-21 22:00 »
umount 狀態下做嗎?