lkml.org 
[lkml]   [2001]   [May]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectO_TRUNC problem on a full filesystem
I am not sure if it should be classified as a bug, that's why I am calling it a
problem. Here is the description:

If the filesystem is full, obviously, I can't write anything to that any
longer. But if I open a file with O_TRUNC flag set, the file will be truncated.
Any program that opens a file with O_TRUNC flag set, wishes to write something
there later on. But because the filesystem is full, it can't write. It would
definitely happen if the file is not huge (TESTED). But I am not sure what
happens if the file _is_ huge (NOT TESTED).

I lost configuration files of a few programs this way. While exiting, they
opened their conf files with O_TRUNC flag but couldn't write anything there.

The kernel in use is 2.4.4.

--manas
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 12:53    [W:0.091 / U:5.028 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site