Administrace komentářů

Diky za rychlu odpoved. Ext4 som vytvoril s novou instalaciou suse 11.2. Povodne som mal ext3 a 11.1. Takze cela particia bola preformatovana na ext4, ziadna konverzia.

Vmware/Win sa sice nenacitava z vmdk na tom ext4, ale vmware si otvori asi 6 suborov a to vytazi hostitelsky system.

Takto nejak sa tie subory zobrazuju v iotope:

vmware-vmx -ssnapshot.numRollingTiers=0 -sRemoteDisplay.vnc.enabled=FALSE -s vmx.stdio.keep=TRUE -# product=8;name=VMware Player;version=3.0.0;buildnumber=203739;l

kjournald2 zapisuje stale nieco, ale ked nemam vmware spustene, tak berie asi 2-3% a je aj tak najviac IO berucim programom.

Ten writeback je trochu zlozitejsie nastavit, nez som si myslel:

The problem is, that you cannot just add data=writeback to your fstab entry and expect everything to work well.

If you look at your logs, you will see that the system complains when mounting the root fs because it cannot change the journaling model by itself.

It mounts the fs read-only, and it just happens that it is X that is the first process in the normal bootup sequence that throws a complete wobbly on account of this.

You need to use tune2fs to change the journal if you really want to do this.

With the root partition mounted readonly (e.g., after one of your failed boot attempts -- but MAKE SURE IT IS RO) do:

# tune2fs -o journal_data_writeback /dev/sdXY (where sdXY is the partition of interest)

Then, reboot, and all should work. Look at my /etc/fstab for a system based on an ssd and you will see that it can work.

eurgain@juno:~$ cat /etc/fstab UUID=57db94de-99f2-227a-83fe-3ca75c4d7f6e / ext4 noatime,barrier=0,data=writeback,nobh,commit=100,nouser_xattr 0 1

2 priklady ako to vyzera ked vo vmware otvaram nejaky binarny subor - pdf, doc...

Total DISK READ: 0 B/s | Total DISK WRITE: 192.03 K/s
  PID USER      DISK READ  DISK WRITE   SWAPIN    IO>    COMMAND
  274 root           0 B/s  134.42 K/s  0.00 % 62.19 % [kjournald2]
30432 tomas          0 B/s   49.93 K/s  0.00 %  0.00 % vmware-vmx -ssnapshot.numRollingTiers=0 -sRemoteDisplay.vnc.enabled=FALSE -s vmx.stdio.keep=TRUE -# product=8;name=VMware Player;version=3.0.0;buildnumber=203739;l
30440 tomas          0 B/s    7.68 K/s  0.00 %  0.00 % vmware-vmx -ssnapshot.numRollingTiers=0 -sRemoteDisplay.vnc.enabled=FALSE -s vmx.stdio.keep=TRUE -# product=8;name=VMware Player;version=3.0.0;buildnumber=203739;l
    1 root           0 B/s       0 B/s  0.00 %  0.00 % init [5]
    2 root           0 B/s       0 B/s  0.00 %  0.00 % [kthreadd]
    3 root           0 B/s       0 B/s  0.00 %  0.00 % [migration/0]
    4 root           0 B/s       0 B/s  0.00 %  0.00 % [ksoftirqd/0]
    5 root           0 B/s       0 B/s  0.00 %  0.00 % [watchdog/0]
    6 root           0 B/s       0 B/s  0.00 %  0.00 % [migration/1]
    7 root           0 B/s       0 B/s  0.00 %  0.00 % [ksoftirqd/1]
    8 root           0 B/s       0 B/s  0.00 %  0.00 % [watchdog/1]
    9 root           0 B/s       0 B/s  0.00 %  0.00 % [events/0]
   10 root           0 B/s       0 B/s  0.00 %  0.00 % [events/1]
   11 root           0 B/s       0 B/s  0.00 %  0.00 % [netns]
   12 root           0 B/s       0 B/s  0.00 %  0.00 % [async/mgr]
   13 root           0 B/s       0 B/s  0.00 %  0.00 % [kintegrityd/0]
   14 root           0 B/s       0 B/s  0.00 %  0.00 % [kintegrityd/1]
   15 root           0 B/s       0 B/s  0.00 %  0.00 % [kblockd/0]
   16 root           0 B/s       0 B/s  0.00 %  0.00 % [kblockd/1]
   17 root           0 B/s       0 B/s  0.00 %  0.00 % [kacpid]
   18 root           0 B/s       0 B/s  0.00 %  0.00 % [kacpi_notify]
   19 root           0 B/s       0 B/s  0.00 %  0.00 % [kacpi_hotplug]
   20 root           0 B/s       0 B/s  0.00 %  0.00 % [ata/0]
   21 root           0 B/s       0 B/s  0.00 %  0.00 % [ata/1]
   22 root           0 B/s       0 B/s  0.00 %  0.00 % [ata_aux]
   23 root           0 B/s       0 B/s  0.00 %  0.00 % [ksuspend_usbd]
   24 root           0 B/s       0 B/s  0.00 %  0.00 % [khubd]
   25 root           0 B/s       0 B/s  0.00 %  0.00 % [kseriod]
   26 root           0 B/s       0 B/s  0.00 %  0.00 % [kondemand/0]
   27 root           0 B/s       0 B/s  0.00 %  0.00 % [kondemand/1]
   28 root           0 B/s       0 B/s  0.00 %  0.00 % [khelper]
   29 root           0 B/s       0 B/s  0.00 %  0.00 % [khungtaskd]
   32 root           0 B/s       0 B/s  0.00







Total DISK READ: 498.48 K/s | Total DISK WRITE: 1671.82 K/s
  PID USER      DISK READ  DISK WRITE   SWAPIN    IO>    COMMAND
  274 root           0 B/s  149.54 K/s  0.00 % 99.99 % [kjournald2]
32097 root           0 B/s  671.03 K/s  0.00 % 99.99 % [pdflush]
30439 tomas     111.20 K/s       0 B/s  0.00 % 34.86 % vmware-vmx -ssnapshot.numRollingTiers=0 -sRemoteDisplay.vnc.enabled=FALSE -s vmx.stdio.keep=TRUE -# product=8;name=VMware Player;version=3.0.0;buildnumber=203739;l
30440 tomas      34.51 K/s       0 B/s  0.00 % 24.86 % vmware-vmx -ssnapshot.numRollingTiers=0 -sRemoteDisplay.vnc.enabled=FALSE -s vmx.stdio.keep=TRUE -# product=8;name=VMware Player;version=3.0.0;buildnumber=203739;l
30432 tomas     256.91 K/s  640.35 K/s  0.00 % 19.75 % vmware-vmx -ssnapshot.numRollingTiers=0 -sRemoteDisplay.vnc.enabled=FALSE -s vmx.stdio.keep=TRUE -# product=8;name=VMware Player;version=3.0.0;buildnumber=203739;l
30438 tomas      95.86 K/s       0 B/s  0.00 % 16.31 % vmware-vmx -ssnapshot.numRollingTiers=0 -sRemoteDisplay.vnc.enabled=FALSE -s vmx.stdio.keep=TRUE -# product=8;name=VMware Player;version=3.0.0;buildnumber=203739;l
30429 tomas          0 B/s  210.89 K/s  0.00 %  0.00 % vmware-vmx -ssnapshot.numRollingTiers=0 -sRemoteDisplay.vnc.enabled=FALSE -s vmx.stdio.keep=TRUE -# product=8;name=VMware Player;version=3.0.0;buildnumber=203739;l
    1 root           0 B/s       0 B/s  0.00 %  0.00 % init [5]
    2 root           0 B/s       0 B/s  0.00 %  0.00 % [kthreadd]
    3 root           0 B/s       0 B/s  0.00 %  0.00 % [migration/0]
    4 root           0 B/s       0 B/s  0.00 %  0.00 % [ksoftirqd/0]
    5 root           0 B/s       0 B/s  0.00 %  0.00 % [watchdog/0]
    6 root           0 B/s       0 B/s  0.00 %  0.00 % [migration/1]
    7 root           0 B/s       0 B/s  0.00 %  0.00 % [ksoftirqd/1]
    8 root           0 B/s       0 B/s  0.00 %  0.00 % [watchdog/1]
    9 root           0 B/s       0 B/s  0.00 %  0.00 % [events/0]
   10 root           0 B/s       0 B/s  0.00 %  0.00 % [events/1]
   11 root           0 B/s       0 B/s  0.00 %  0.00 % [netns]
   12 root           0 B/s       0 B/s  0.00 %  0.00 % [async/mgr]
   13 root           0 B/s       0 B/s  0.00 %  0.00 % [kintegrityd/0]
   14 root           0 B/s       0 B/s  0.00 %  0.00 % [kintegrityd/1]
   15 root           0 B/s       0 B/s  0.00 %  0.00 % [kblockd/0]
   16 root           0 B/s       0 B/s  0.00 %  0.00 % [kblockd/1]
   17 root           0 B/s       0 B/s  0.00 %  0.00 % [kacpid]
   18 root           0 B/s       0 B/s  0.00 %  0.00 % [kacpi_notify]
   19 root           0 B/s       0 B/s  0.00 %  0.00 % [kacpi_hotplug]
   20 root           0 B/s       0 B/s  0.00 %  0.00 % [ata/0]
   21 root           0 B/s       0 B/s  0.00 %  0.00 % [ata/1]
   22 root           0 B/s       0 B/s  0.00 %  0.00 % [ata_aux]

V normalnej notebookovej praci je to celkom svizne, ale ked ked zapnem vmware s windowsami z fyzickeho disku, tak ten vmware je asi 10krat pomalsi ako ked som mal ext3.

Jak píšete, windows se načítají z fyzikého disku a nikoliv z vmdk souboru na té ext4. Zde nevidím souvislost.

kjournald2 mi v iotope konstantne zabera 98% IO (strieda sa na prvom mieste s pdflush)

To dělá pouze při zapnutém vmware nebo pořád?

da sa bezpecne konvertovat ext4 na ext3?

Bezpečně ano, zazálohovat a vytvořit ext3. Zkonvertovat na místě to nejde.

Ak tam dam writeback tak tym vypnem zurnal?

Nikoliv. Jen se změní pořadí zápisu dat na disk. Writeback zajišťuje konzistenci metadat na FS, ovšem ne samotných dat. Tento mód je obecně nejrychlejší. Ostatní souborové systémy žurnálují právě takto. Můžete to zkusit nastavit a uvidíte.

Ma nejaky iny parameter vpliv na kjournald2 IO operacie?

U ext3 to byl parametr commit, ale ten už u ext4 postrádá smysl.

Zkuste prosím popsat jakým postupem jste konvertoval tu ext3 na 4. Nově vytvořený fs, nebo nějaký jiný postup?