From: Manas Garg <mls@chakpak.net>
To: linux-kernel@vger.kernel.org
Subject: O_TRUNC problem on a full filesystem
Date: Wed, 23 May 2001 11:43:18 +0530 [thread overview]
Message-ID: <20010523114318.A8336@cygsoft.com> (raw)
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
next reply other threads:[~2001-05-23 6:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-23 6:13 Manas Garg [this message]
2001-05-23 9:16 ` OT: O_TRUNC problem on a full filesystem Helge Hafting
2001-05-23 9:55 ` Andrew Morton
2001-05-24 11:16 ` Stephen C. Tweedie
2001-05-24 11:28 ` Andrew Morton
2001-05-24 17:24 ` Andreas Dilger
2001-05-24 18:15 ` Stephen C. Tweedie
2001-05-24 20:26 ` Andreas Dilger
2001-05-25 0:24 ` Andrew Morton
2001-05-25 9:42 ` Stephen C. Tweedie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010523114318.A8336@cygsoft.com \
--to=mls@chakpak.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox