From: Michael Weissenbacher <webmaster@dermichi.com>
To: ReiserFS List <reiserfs-list@namesys.com>
Cc: Joe Orton <jorton@redhat.com>
Subject: Re: EACCESS vs ENOENT for nonexistent files-within-files
Date: Mon, 13 Sep 2004 17:21:32 +0200 [thread overview]
Message-ID: <4145BAFC.6090408@dermichi.com> (raw)
In-Reply-To: <20040913140637.GB29591@redhat.com>
> Hi, we had a bug report that Apache httpd logs a spurious error for
> every file served from a reiser4 filesystem, because httpd assumes that
> /path/to/file/.htaccess (where /path/to/file is a normal file) returns
> ENOENT or ENOTDIR, but reiser4 returns EACCES in this case.
>
> Can someone explain the justification behind reiser4's behaviour?
> httpd's assumption does not seem unreasonable, and EACCES seems to make
> little sense for this error case.
>
i think the problem would be "solved" by mounting the partition with the
nopseudos option. of course, this is not the long-term solution.
regards,
michael
next prev parent reply other threads:[~2004-09-13 15:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-13 14:06 EACCESS vs ENOENT for nonexistent files-within-files Joe Orton
2004-09-13 14:25 ` Wayne Scott
2004-09-13 15:21 ` Michael Weissenbacher [this message]
2004-09-13 16:13 ` Alex Zarochentsev
2004-09-13 18:52 ` Joe Orton
2004-09-13 19:44 ` Nikita Danilov
2004-09-15 10:55 ` evilninja
2004-09-15 11:41 ` Nikita Danilov
2004-09-16 0:00 ` evilninja
2004-09-13 20:58 ` Alex Zarochentsev
-- strict thread matches above, loose matches on Subject: below --
2004-09-15 13:18 Paul Wagland
2004-09-15 14:04 ` Hans Reiser
2004-09-15 14:16 ` Paul Wagland
2004-09-15 15:12 ` Nikita Danilov
2004-09-15 14:45 ` Nikita Danilov
2004-09-15 16:15 ` daniel.poelzleithner
2004-09-15 22:40 ` Hans Reiser
2004-09-16 19:55 ` Toby Dickenson
[not found] ` <2f9ccaae04091615395cfd0730@mail.gmail.com>
2004-09-16 22:40 ` Perry Kundert
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=4145BAFC.6090408@dermichi.com \
--to=webmaster@dermichi.com \
--cc=jorton@redhat.com \
--cc=reiserfs-list@namesys.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.