Ubuntu8.10下修復FC7系統的home分區

 
由於公司服務器/home/httpd/web下newjw1該文件夾經常更新文件,用戶訪問該目錄較多,開機無法啓動出現,
no fstab.sys , mount ....
/home contains a file system with errors,check forced.在此處掃描過不去在3.4%。
沒辦法只好將該硬盤掛載到一臺ubuntu的機器上。
#sudo mkdir /media/_home
#sudo mount /dev/sdb2  /media/_home
 
juwang@juwang-jiangwei:~$ sudo fsck -y /dev/sdb2
fsck 1.41.3 (12-Oct-2008)
fsck: fsck.: not found
fsck: Error 2 while executing fsck. for /dev/sdb2
juwang@juwang-jiangwei:~$ sudo fsck.ext3 -y /dev/sdb2   --ext3文件系統。
e2fsck 1.41.3 (12-Oct-2008)
fsck.ext3: Superblock invalid, trying backup blocks...
Adding dirhash hint to filesystem.
/home contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Free blocks count wrong for group #3 (692, counted=138).
Fix? yes
Free blocks count wrong for group #4 (4294, counted=840).
Fix? yes
Free blocks count wrong for group #5 (1817, counted=229).
Fix? yes
Free blocks count wrong for group #6 (761, counted=73).
Fix? yes
Free blocks count wrong for group #38 (523, counted=17848).
Fix? yes
Free blocks count wrong for group #39 (1174, counted=18157).
Fix? yes
Free blocks count wrong for group #40 (206, counted=628).
Fix? yes
Free blocks count wrong for group #41 (4, counted=11).
Fix? yes
Free blocks count wrong for group #43 (3, counted=5).
Fix? yes
Free blocks count wrong for group #47 (108, counted=1825).
Fix? yes
Free blocks count wrong for group #48 (171, counted=6517).
Fix? yes
Free blocks count wrong for group #49 (100, counted=17152).
Fix? yes
Free blocks count wrong for group #50 (0, counted=12339).
Fix? yes
Free blocks count wrong for group #51 (3125, counted=6137).
Fix? yes
Free blocks count wrong for group #52 (1363, counted=1308).
Fix? yes
Free blocks count wrong for group #53 (31730, counted=6).
Fix? yes
Free blocks count wrong for group #54 (31741, counted=5).
Fix? yes
Free blocks count wrong for group #55 (31741, counted=5).
Fix? yes
Free blocks count wrong for group #56 (31740, counted=4).
Fix? yes
Free blocks count wrong for group #57 (31742, counted=6).
Fix? yes
Free blocks count wrong for group #58 (31741, counted=14630).
Fix? yes
Free blocks count wrong for group #755 (2672, counted=388).
Fix? yes
Free blocks count wrong for group #756 (15982, counted=0).
Fix? yes
Free blocks count wrong for group #757 (14848, counted=0).
Fix? yes
Free blocks count wrong for group #758 (13184, counted=0).
Fix? yes
Free blocks count wrong for group #759 (17927, counted=25).
Fix? yes
Free blocks count wrong for group #760 (10494, counted=134).
Fix? yes
Free blocks count wrong for group #761 (14563, counted=1864).
Fix? yes
Free blocks count wrong for group #762 (11566, counted=84).
Fix? yes
Free blocks count wrong for group #763 (11351, counted=149).
Fix? yes
Free blocks count wrong for group #764 (11538, counted=1899).
Fix? yes
Free blocks count wrong (15484818, counted=15258323).
Fix? yes
Free inodes count wrong for group #3 (31262, counted=31261).
Fix? yes
Free inodes count wrong for group #38 (31279, counted=32722).
Fix? yes
Directories count wrong for group #38 (576, counted=23).
Fix? yes
Free inodes count wrong for group #39 (25718, counted=32525).
Fix? yes
Directories count wrong for group #39 (1442, counted=2).
Fix? yes
Free inodes count wrong for group #40 (30446, counted=30549).
Fix? yes
Directories count wrong for group #40 (27, counted=16).
Fix? yes
Free inodes count wrong for group #48 (28530, counted=32446).
Fix? yes
Directories count wrong for group #48 (894, counted=2).
Fix? yes
Free inodes count wrong for group #51 (32099, counted=32236).
Fix? yes
Directories count wrong for group #51 (26, counted=4).
Fix? yes
Free inodes count wrong for group #52 (31226, counted=31688).
Fix? yes
Directories count wrong for group #52 (66, counted=8).
Fix? yes
Free inodes count wrong for group #755 (25561, counted=25559).
Fix? yes
Free inodes count wrong (25298330, counted=25311195).
Fix? yes

/home: ***** FILE SYSTEM WAS MODIFIED *****
/home: 313381/25624576 files (10.1% non-contiguous), 10341254/25599577 blocks
 
fsck的語法如下:
  fsck (-F fstype) (-v) (-m) (-special…)
  fsck (-F fstype) (-v) (-y|Y|n|N)
  (-o fstype options) (special…)
  其中:
  -F fstype : 說明被檢查的文件系統的類型
  -v : 返回完成的命令行,但不運行
  -y|Y: 對所有問題均回答Yes
  -n|N: 對所有問題均回答No
  -m: 對文件系統進行檢查,不修覆文件系統,
  如果文件系統經檢查後是可安裝的,則顯示
  ufs fsck : sanity check : /dev/rdsk/c0t0d0s0 okay.
  -o: 文件系統類型選項,選項由逗號分隔,
  最常用的選項有兩個:
  P: 整理(preen)模式
  F: 強制檢查模式,此選項忽略文件系統狀態標誌。
  
  運行fsck後,該命令會分6個階段對文件系統
  進行檢查,這六個階段分別是:
  階段1: 檢查塊和塊的大小
  階段2: 檢查路徑名
  階段3: 檢查連接性
  階段4: 檢查參考記數
  階段5: 檢查自由塊列表
  階段6: 補救自由塊列表
  ---- fsck在對每個階段進行檢查時,如果發現錯誤,會提示用戶進行修改,常見的一些錯誤有: 1) 移去一個沒有相關文件的目錄入口
  
  ---- 這時用戶可以回答Yes或Y來刪除該目錄入口。
  
  ---- 2) 重連接一個已分配但不能訪問的文件:
  
  ---- fsck找到了一個已分配的I節點,但卻不可訪問(該節點沒與任何目錄連接),這時一般對fsck的"RECONNECT?"回答Yes,即把該I節點連接到lost+found目錄下,文件名即是I節點號,之後管理員應檢查該文件類型,判明該文件用途,再將該文件拷貝到相應目錄下。
  
  ---- 3) 連接數調整
  
  ---- 在交互方式下,fsck若發現連接數不一致,將詢問用戶採取何種行動,本例發現一目錄的I節點連接數與該目錄的真實連接數不一致。
  
  ---- 這時用戶應該回答Yes或Y來改正連接數。
  
  ---- 4) 自由塊表不一致
  
  ---- fsck查出未分配塊數與超級塊中所給出的自由塊表不一致。
  
  ---- 這時用戶應該回答Yes或Y來修正超級塊。
  
  ---- 從上面的出錯信息和處理方法可以發現,對於fsck詢問的問題大多數情況下都可以用Yes來回答,所以在實際應用時,可以用" -y"選項來執行該命令對硬盤進行檢查和修復。
發表評論
所有評論
還沒有人評論,想成為第一個評論的人麼? 請在上方評論欄輸入並且點擊發布.
相關文章