Hi guys,
>> There are mount options that force immediate writes. Would it be sync?
>
>I guess theres' a 50 page how to about that somewhere...I'll have to check...
I haven't been following this discussion but yes, there's a ext2 attribute (chattr
+S) that forces immediate writes.
---------------From `man chattr':---------------
When a file with the 'A' attribute set is modified, its atime record is not modi-
fied. This avoids a certain amount of disk I/O for laptop systems.
A file with the `a' attribute set can only be open in append mode for writing.
Only the superuser can set or clear this attribute.
A file with the `c' attribute set is automatically compressed on the disk by the
kernel. A read from this file returns uncompressed data. A write to this file com-
presses data before storing them on the disk.
A file with the `d' attribute set is not candidate for backup when the dump(8) pro-
gram is run.
A file with the `i' attribute cannot be modified: it cannot be deleted or renamed,
no link can be created to this file and no data can be written to the file. Only
the superuser can set or clear this attribute.
When a file with the `s' attribute set is deleted, its blocks are zeroed and writ-
ten back to the disk.
When a file with the `S' attribute set is modified, the changes are written syn-
chronously on the disk; this is equivalent to the `sync' mount option applied to a
subset of the files.
When a file with the `u' attribute set is deleted, its contents are saved. This
allows the user to ask for its undeletion.
-------------------------------------------
Please excuse me if this wasn't what you was talking about.
//Björn.
--
To unsubscribe from this list, send a message to [EMAIL PROTECTED]
with the command "unsubscribe linux-embedded" in the message body.
For more information, see <http://waste.org/mail/linux-embedded>.
