From: Jan Kasprzak <kas@fi.muni.cz>
To: Jakob Oestergaard <jakob@unthought.net>,
linux-kernel@vger.kernel.org, kruty@fi.muni.cz
Subject: Re: XFS: inode with st_mode == 0
Date: Thu, 9 Dec 2004 15:07:25 +0100 [thread overview]
Message-ID: <20041209140725.GQ9994@fi.muni.cz> (raw)
In-Reply-To: <20041209135322.GK347@unthought.net>
Jakob Oestergaard wrote:
: > I have seen the strange problem on our NFS server: yesterday I have
: > found an empty file owned by UID 0/GID 0 and st_mode == 0 in my home
: > directory (ls -l said "?--------- 1 root root 0 <date> <filename>").
: > The <filename> was correct name of a temporary file used by one of my
: > cron jobs (and the cron job was failing because it could not rewrite the file).
: > It was not possible to write to this file, so I have renamed it
: > as "badfile" for further investigation (using mv(1) on the NFS server itself).
:
: Known problem
:
: http://lkml.org/lkml/2004/11/23/283
:
: Seems there is no solution yet
:
: http://lkml.org/lkml/2004/11/30/145
:
Hmm, thanks for the info.
In the meantime, I was able to reproduce this by running the
following script for an hour or so on Solaris 8 NFS client:
#!/bin/bash
FILE="testfile"
set -e
while :
do
rm -f "$FILE"
sleep 1
echo trubka > "$FILE"
sleep 1
cat "$FILE">/dev/null
done
After some time I've got this:
emptyfile.sh: testfile: Invalid argument
$ ls -l testfile
?--------- 1 root root 0 Dec 9 14:51 testfile
-Yenya
--
| Jan "Yenya" Kasprzak <kas at {fi.muni.cz - work | yenya.net - private}> |
| GPG: ID 1024/D3498839 Fingerprint 0D99A7FB206605D7 8B35FCDE05B18A5E |
| http://www.fi.muni.cz/~kas/ Czech Linux Homepage: http://www.linux.cz/ |
> Whatever the Java applications and desktop dances may lead to, Unix will <
> still be pushing the packets around for a quite a while. --Rob Pike <
next prev parent reply other threads:[~2004-12-09 14:08 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-09 12:59 Jan Kasprzak
2004-12-09 13:53 ` Jakob Oestergaard
2004-12-09 14:07 ` Jan Kasprzak [this message]
2004-12-09 21:54 ` Christoph Hellwig
2004-12-14 23:40 ` Jakob Oestergaard
2004-12-21 18:43 ` Jan Kasprzak
2004-12-22 8:41 ` Jakob Oestergaard
2004-12-22 18:23 ` Christoph Hellwig
2004-12-23 15:01 ` Jakob Oestergaard
2005-01-04 8:48 ` Jakob Oestergaard
2005-01-05 11:34 ` Christoph Hellwig
2005-01-14 18:14 ` David Greaves
2005-01-14 18:23 ` Jakob Oestergaard
2005-01-15 2:09 ` Nathan Scott
2005-01-17 0:53 ` Jakob Oestergaard
2005-01-16 13:51 ` Christoph Hellwig
2005-01-17 10:07 ` Jakob Oestergaard
2005-01-17 11:55 ` Jan-Frode Myklebust
2005-01-17 13:48 ` Anders Saaby
2005-01-17 21:31 ` journaled filesystems -- known instability; Was: " Jeffrey Hundstad
2005-01-17 20:54 ` Alan Cox
2005-01-20 22:30 ` Jeffrey E. Hundstad
2005-01-25 12:47 ` Stephen C. Tweedie
2005-01-25 15:09 ` Jeffrey Hundstad
2005-01-25 15:37 ` Stephen C. Tweedie
2005-01-28 20:15 ` Jeffrey E. Hundstad
2005-01-28 21:00 ` Stephen C. Tweedie
2005-01-28 21:06 ` Jeffrey E. Hundstad
2005-01-18 11:45 ` Jan Kasprzak
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=20041209140725.GQ9994@fi.muni.cz \
--to=kas@fi.muni.cz \
--cc=jakob@unthought.net \
--cc=kruty@fi.muni.cz \
--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®