如何避免 server 變成 read－only film system？

fatdog

學左用 linux 咁耐
d server 用用下，真係久唔久又會突然變 read only ...

有時都唔知做錯乜野 ...
有時亦都救唔到 OS 果部份要重裝 ...

其實平時應該點樣去main先避免到呢個情況？

archy

Usually had drive failure to cause the problem ,
ext3 will lock the drive when the drive is not healthy.

If you confirmed the hard drive have no problem ,
you may try to use xfs instead of ext3 ,
I have a xfs server production over 7 years function good.

laueye

ready only 試過一次
最多係ext3 頻繁read write 後
file system 出現file corrupt
之後hang機 or 自動reboot
一定要行fsck

fatdog

ready only 試過一次
最多係ext3 頻繁read write 後
file system 出現file corrupt
之後hang機 or 自動rebo ...
laueye 發表於 2013-9-29 19:00

係咪次次 read－only 都要走去入碟 救？

lazyfai

唔係一定, reboot 佢多數就會用得返, 但好大機會會再出事, 病向淺中醫.

係咪次次 read－only 都要走去入碟 救？
fatdog 發表於 2013-9-29 21:50

jwschow

What kind / model of HDD you are using?

I don't think that this is ext3 problem.

學左用 linux 咁耐
d server 用用下，真係久唔久又會突然變 read only ...

有時都唔知做錯乜野 ...
有時亦 ...
fatdog 發表於 2013-9-29 14:48

fatdog

What kind / model of HDD you are using?

I don't think that this is ext3 problem.
jwschow 發表於 2013-9-30 13:04

ext4
我都有d 機係一直咁多年都冇事

啱啱呢次 。。。 係一堆 GREEN

jwschow

Green and SATA HDD is not suitable for production.  They are for backup only.

If it's I/O intensive, you must use SAS or SCSI HDD.  It's not only due to speed & performance, but also it's entirely different mechanism to read/write.

Always or often, delay write causes the integrity problem of the filesystem. Delay write may be due to sleeping, disk cache, filesystem object cache.  If cached object cannot be committed (for example, power lost, signal lost), the filesystem will be damaged. Then it needs a fsck.  

ext4
我都有d 機係一直咁多年都冇事

啱啱呢次 。。。 係一堆 GREEN
fatdog 發表於 2013-9-30 22:33

uxuq

試過RAID degrade後發生

fatdog

作為新手，有咩係平日需要做 去避免呢個情況？