From: Nuno Silva <nuno.silva@vgertech.com>
To: Rob van Nieuwkerk <robn@verdi.et.tudelft.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4 bug: fifo-write causes diskwrites to read-only fs !
Date: Wed, 28 May 2003 20:22:04 +0100 [thread overview]
Message-ID: <3ED50C5C.9010309@vgertech.com> (raw)
In-Reply-To: <20030528175842.GA13657@verdi.et.tudelft.nl>
Rob van Nieuwkerk wrote:
> Hi all,
>
> It turns out that Linux is updating inode timestamps of fifos (named
> pipes) that are written to while residing on a read-only filesystem.
> It is not only updating in-ram info, but it will issue *physical*
> writes to the read-only fs on the disk !
Hi!
I can't give a solution but the workaround is obvious:
mount -t ramfs none /myFifos
Regards,
Nuno Silva
next prev parent reply other threads:[~2003-05-28 19:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-28 17:58 2.4 bug: fifo-write causes diskwrites to read-only fs ! Rob van Nieuwkerk
2003-05-28 18:52 ` Rob van Nieuwkerk
2003-05-28 19:17 ` Richard B. Johnson
2003-05-28 19:34 ` Rob van Nieuwkerk
2003-05-28 20:22 ` Richard B. Johnson
2003-05-28 20:52 ` Rob van Nieuwkerk
2003-05-30 13:21 ` Stephen C. Tweedie
2003-05-30 14:58 ` Christoph Hellwig
2003-05-30 15:18 ` Stephen C. Tweedie
2003-05-30 16:36 ` Andrew Morton
2003-05-28 19:22 ` Nuno Silva [this message]
2003-05-28 19:37 ` Rob van Nieuwkerk
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=3ED50C5C.9010309@vgertech.com \
--to=nuno.silva@vgertech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robn@verdi.et.tudelft.nl \
/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