24 replies to this topic

[anudanan]

Some people in et-view-support forum have positiv effects with with data=writeback parameter so I think it makes sense to use it as a default parameter for the filesystem on HDD.

Edited by anudanan, 27 January 2012 - 17:55.

[MiLo]

From the ext4 kernel source:

#define EXT4_DEFM_JMODE		 0x0060
#define EXT4_DEFM_JMODE_DATA    0x0020
#define EXT4_DEFM_JMODE_ORDERED 0x0040
#define EXT4_DEFM_JMODE_WBACK   0x0060

Looks like the kernel default is already "writeback". Apparently, mkfs sets the default to ordered on the disk.

[anudanan]

I see you changed the mount call in your script with data=writeback. Is that write. Thank you very much

Edited by anudanan, 27 January 2012 - 21:29.

[familievierfuss]

I tested my ext2 HDD with the ext4 Modul.

1.) No entry in fstab
Disk was not mounted

2.) Entry in fstab with UUID and "AUTO"
Disk mounted with the ext4 Modul, but I had Freezers in the first 20 seconds if the record starts vom Deepstanby or from a HDD-Standby

3.) I installed the ext2 Modul manual and changed the fstab UUID entry to "ext2"
No freezers

So please, don't remove the ext2/3 Moduls from the feed!

Edited by familievierfuss, 30 January 2012 - 10:08.

[familievierfuss]

Some users had formatted there HDD with ext2 and use it with a manual fstab-entry to avoid freezers in records.
Now with the new kernel some of the users reported new freezers in the first seconds of a record.


Whats up, we can't find special ext2/ext3 Moduls on the feed?