From: Matt Gibson <gothick@gothick.org.uk>
To: linux-kernel@vger.kernel.org
Subject: Re: File access error fixed with mount -o remount ?
Date: Wed, 24 Sep 2003 00:09:59 +0100 [thread overview]
Message-ID: <200309240009.59450.gothick@gothick.org.uk> (raw)
In-Reply-To: <3F70CEA3.70905@jpl.nasa.gov>
On Tuesday 23 Sep 2003 23:52, Bryan Whitehead wrote:
> I have run across a problem with files that seem to become randomly
> "broken" but after a "mount -o remount" the files start working normally
> again.
I've had a vaguely similar problem with 2.6.0-test5: recently I've been
compiling KDE over a period of a few days. The first couple of days I was
running test4, and everything was fine. Then I upgraded to test5, and three
times now I've had particular executables become unusable. For example,
yesterday, egrep just stopped working. This stopped the KDE build, and
testing it by hand, I found that running "egrep" gave me the error "text
file busy." I couldn't find any way of making it work again except a
reboot.
Today it was "sed" that stopped being runnable with the same error message.
I didn't try a remount (at the moment, my system is one big / partition.
Yeah, I know...) Again, sed didn't become runnable again until I rebooted.
Has anyone else seen this weirdness? It's vanilla 2.6.0-test5, with
reiserfs.
M
--
"It's the small gaps between the rain that count,
and learning how to live amongst them."
-- Jeff Noon
prev parent reply other threads:[~2003-09-23 23:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-23 22:52 Bryan Whitehead
2003-09-23 23:09 ` Matt Gibson [this message]
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=200309240009.59450.gothick@gothick.org.uk \
--to=gothick@gothick.org.uk \
--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
all inboxes | Powered by JetHome®