[an error occurred while processing this directive] [an error occurred while processing this directive][an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] (none) [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive][an error occurred while processing this directive]
[an error occurred while processing this directive][an error occurred while processing this directive] [an error occurred while processing this directive][an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] (none) [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive][an error occurred while processing this directive]![]() |
![]() |
![]() |
|||||||||||||||||||||||||
|
|||||||||||||||||||||||||||
![]() |
![]() |
![]() |
I sslug.teknik, skrev Michael Rasmussen: > > Er der nogen der har praktiske erfaringer med at bruge data=writeback > > som mountoption til ext3. Ifølge man-siderne skulle det give noget > > performance. I det system jeg overvejer at gøre det på kører der p.t. > > en mysql-database og jeg ville helst ikke hvis den tog permanent > > skade af at der var nogle der kappede strømmen.. er der risiko for > > det? > > > > Jeg har anvendt denne option (data=journal), da det skulle give den > bedste performance, når der er mange samtidige skrivninger og læsninger > til samme disk - bl.a. database og mail servere. Det passer jo ikke.. se nedenfor: > Andrew Morton: http://www.ibm.com/developerworks/library/l-fs8.html Quote: data=writeback mode In data=writeback mode, ext3 doesn't do any form of data journaling at all, providing you with similar journaling found in the XFS, JFS, and ReiserFS filesystems (metadata only). As I explained in my previous article, this could allow recently modified files to become corrupted in the event of an unexpected reboot. Despite this drawback, data=writeback mode should give you the best ext3 performance under most conditions. Jesper -- ./Jesper Krogh, sslug@sslug, Jabber ID: sslug@sslug
![]() |
![]() |
![]() |
||||||||||||
|
||||||||||||||
![]() | ||||||||||||||
|
||||||||||||||
![]() |
![]() |
![]() |