Skip to contentSkip to conversation

OMFS filesystem version 3

PATCH Bodo Eggert 1 participant 1 message Apr 16, 2008 3 messages not in the archive VFS

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

#3 lore raw
Quoted 13 lines · Anton Altaparmakov
Quoted 11 lines · Szabolcs Szakacsits
Quoted 1 line · On Mon, 14 Apr 2008 Anton Altaparmakov wrote:

(and under no-one I include the OOM killer for example!)

The OOM killer can be configured and if the fs still uses too much memory
then probably it's better to be killed/restarted with journaling support.
The important here would be the kernel finally fixing the non-sync behavior
when it clams to do so (see recent kernel threads).

Quoted 3 lines

You don't get the point. Any process in the system can be using too much memory and trigger the OOM killer even when the FS is behaving just fine...

Just set /proc/$pid/oom_adj to -17.