From: Helge Hafting <helgehaf@aitel.hist.no>
To: linux-kernel@vger.kernel.org
Subject: 2.6.11-rc5-mm1 nfs oddity, file creation => "no such file"
Date: Wed, 2 Mar 2005 20:14:27 +0100 [thread overview]
Message-ID: <20050302191427.GA9383@hh.idb.hist.no> (raw)
I observed an oddity on a nfs-mounted fs while using 2.6.11-rc5-mm1.
I tried to save a file from xfig, and got an error message about a
nonexisting file. Now apps may have their own bugs, so I
retried in the shell:
$ cat > newfile
newfile: No such file or directory
$
Eh - of course it didn't exist - I was trying to create it!
This also resulted in "newfile" being created with size 0.
Repeating the "cat > newfile" worked fine once the zero-length
file existed. Unfortunately, xfig always removes files before overwriting
so it couldn't save on the nfs volume at all.
File creation by "touch filename" worked flawlessly.
After this I rebooted into 2.6.11-rc3-mm1 which haven't shown this problem
so far. There were nothing in "dmesg" when this happened, other
than a message about "mount" being older than the kernel.
I can try to recreate the problem if necessary.
Helge Hafting
next reply other threads:[~2005-03-02 19:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-02 19:14 Helge Hafting [this message]
2005-03-02 21:37 ` 2.6.11-rc5-mm1 nfs oddity, file creation => "no such file" Andrew Morton
2005-03-03 10:35 ` Helge Hafting
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=20050302191427.GA9383@hh.idb.hist.no \
--to=helgehaf@aitel.hist.no \
--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