All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carsten Gaebler <ezinye-zinto@snakefarm.org>
To: linux-kernel@vger.kernel.org
Cc: linux-xfs@oss.sgi.com
Subject: Re: 2.4.25 XFS can't create files
Date: Fri, 02 Apr 2004 13:34:14 +0200	[thread overview]
Message-ID: <406D4FB6.4070301@snakefarm.org> (raw)
In-Reply-To: <20040402093238.GA28931@dingdong.cryptoapps.com>

Chris Wedgwood wrote:
> I suspect it's not MPT related.  I'm not farmiliar with stock 2.4.25
> but assume the XFS merge went OK and everything is sane.  Any chance
> you can test with a CVS kernel from oss.sgi.com to rule out the
> (probably minor) differences there?

The SGI kernel works fine. Thanks for the hint.

> strace shows open/creat failing?

Yes.

open("/mnt/xfs/foo", O_WRONLY|O_NONBLOCK|O_CREAT|O_NOCTTY|O_LARGEFILE, 
0666) = -1 EACCES (Permission denied)

 > there are also no ACLs and/or
> security modules involved are there?

Nope.

cg.

  reply	other threads:[~2004-04-02 11:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-02  8:14 2.4.25 XFS can't create files Carsten Gaebler
2004-04-02  9:32 ` Chris Wedgwood
2004-04-02 11:34   ` Carsten Gaebler [this message]
2004-04-05  8:05 ` Nathan Scott

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=406D4FB6.4070301@snakefarm.org \
    --to=ezinye-zinto@snakefarm.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@oss.sgi.com \
    /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.