From: Jakob Oestergaard <jakob@unthought.net>
To: Christoph Hellwig <hch@infradead.org>,
Jan Kasprzak <kas@fi.muni.cz>,
linux-kernel@vger.kernel.org, kruty@fi.muni.cz
Subject: Re: XFS: inode with st_mode == 0
Date: Wed, 15 Dec 2004 00:40:12 +0100 [thread overview]
Message-ID: <20041214234012.GX347@unthought.net> (raw)
In-Reply-To: <20041209215414.GA21503@infradead.org>
On Thu, Dec 09, 2004 at 09:54:14PM +0000, Christoph Hellwig wrote:
...
>
> If it's really st_mode I suspect it's a different problem. Can you retry
> with current oss.sgi.com CVS (or the patch below). Note that this patch
> breaks xfsdump unfortunately, we're looking into a fix.
I'm running plain 2.6.9 plus the patch you sent now.
So far, the server hasn't hosed itself (and it's been running for almost
half an hour - woohoo)
Now I can check out CVS trees without getting files with weird ownership
and undeletable directories (which as *extremely* common before - in
fact, earlier today before I applied the patch, I was unable to complete
a cvs checkout of a moderately large software project).
I guess this is a thumbs up for your patch so far :)
> > > Maybe some data is flushed in an incorrect order?
> >
> > Maybe :)
>
> No, the problem I've fixed was related to XFS getting the inode version
> number wrong - or at least different than NFSD expects.
I have seen problems that your patch probably won't fix (like
undeletable directories randomly occuring on ext3 filesystems as well -
seems that once the dcache gets confused, it *really* gets confused).
Let's see how the box fares with your patch - I'll report back on new
bugs as I find them.
--
/ jakob
next prev parent reply other threads:[~2004-12-15 0:18 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-09 12:59 XFS: inode with st_mode == 0 Jan Kasprzak
2004-12-09 13:53 ` Jakob Oestergaard
2004-12-09 14:07 ` Jan Kasprzak
2004-12-09 21:54 ` Christoph Hellwig
2004-12-14 23:40 ` Jakob Oestergaard [this message]
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=20041214234012.GX347@unthought.net \
--to=jakob@unthought.net \
--cc=hch@infradead.org \
--cc=kas@fi.muni.cz \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.