From: "Parag Warudkar" <parag.lkml@gmail.com>
To: "Tomasz Chmielewski" <mangoo@wpkg.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Stale NFS File Handle but !NFS
Date: Thu, 23 Oct 2008 18:54:32 -0400 [thread overview]
Message-ID: <f7848160810231554ra4dd0d4i2d81c817e04c8cbc@mail.gmail.com> (raw)
In-Reply-To: <4900FA92.4000409@wpkg.org>
On Thu, Oct 23, 2008 at 6:28 PM, Tomasz Chmielewski <mangoo@wpkg.org> wrote:
>> Anyone got an idea why I am getting the below error with today's git
>> while compiling the kernel?
>>
>> LD arch/x86/vdso/built-in.o
>> scripts/Makefile.build:373: net/netfilter/.xt_mac.o.cmd: Stale NFS file
>> handle
>> make[2]: stat: net/netfilter/.xt_mac.o.cmd: Stale NFS file handle
>> make[2]: *** No rule to make target `net/netfilter/.xt_mac.o.cmd'. Stop.
>> make[1]: *** [net/netfilter] Error 2
>> make: *** [net] Error 2
>> parag@parag-desktop:~/kernel-dev/linux-2.6-wk$ rm
>> net/netfilter/.xt_mac.o.cmd
>> rm: cannot remove `net/netfilter/.xt_mac.o.cmd': Stale NFS file handle
>> parag@parag-desktop:~/kernel-dev/linux-2.6-wk$ sudo rm
>> net/netfilter/.xt_mac.o.cmd
>>
>> Even trying 'sudo rm -f' on that file gives the same error.
>>
>> I am not using NFS at all which makes this one sound weird!
>
> Broken filesystem?
>
> You may try fscking the filesystem.
>
Yep - just finished that and got unused/deleted inode errors plus bunch more.
That's weird though since this is a new machine and new install - time
to do a memtest followed by going back to stable kernel.
Thanks
Parag
next prev parent reply other threads:[~2008-10-23 22:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-23 22:28 Tomasz Chmielewski
2008-10-23 22:54 ` Parag Warudkar [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-10-23 21:58 Parag Warudkar
2008-10-30 0:56 ` Andrew Morton
2008-10-30 1:24 ` Parag Warudkar
2008-10-30 8:02 ` Christoph Hellwig
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=f7848160810231554ra4dd0d4i2d81c817e04c8cbc@mail.gmail.com \
--to=parag.lkml@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mangoo@wpkg.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®