public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Andrey Vul <andrey.vul@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: dir is rwx but can't create file
Date: Thu, 29 Jul 2010 00:23:54 +0000	[thread overview]
Message-ID: <AANLkTik_cpGZSZMbh1g+0AkibiV6BfJXvDgLzZghkUhs@mail.gmail.com> (raw)
In-Reply-To: <4C50AB2A.3020601@gmail.com>

If / was mounted ro, touch would output strerror(EROFS), not strerror(ENOENT)

On 2010-07-28, Bill Longman <bill.longman@gmail.com> wrote:
> On 07/28/2010 01:52 PM, Alan McKinnon wrote:
>> On Wednesday 28 July 2010 22:20:17 Andrey Vul wrote:
>>> Creating files in /tmp, /etc, /lib32, and /var return ENOENT (touch
>>> /tmp/foo => strerror(ENOENT)).
>>> However, this is done as root and the dirs are marked 755 root:root.
>>> df -i shows only 2% inode usage.
>>> Any explanation as to why a rwx-ed dir can't be written to? This is
>>> breaking quite a few of the init scripts.
>>>
>>> --
>>> Andrey Vul
>>> begin-base64 600 sig
>>> bXNuLCBob21lOiBhbmRyZXkudnVsQGdtYWlsLmNvbQ0KdSBvZiB0OiBhbmRyZXkudnVsQHV0b3J
>>> v bnRvLmNhDQpzbXMsIHZvaWNlbWFpbDogNDE2MzAzOTkyMw0K
>>> `
>>> end
>>
>> sounds like / is mounted read-only
>
> Do read-only filesystems typically reply ENOENT when trying to create a
> file? It's usually something like "read-only filesystem" in that case.
> ENOENT means it can't even find the file.
>
>

-- 
Sent from my mobile device

Andrey Vul
begin-base64 600 sig
bXNuLCBob21lOiBhbmRyZXkudnVsQGdtYWlsLmNvbQ0KdSBvZiB0OiBhbmRyZXkudnVsQHV0b3Jv
bnRvLmNhDQpzbXMsIHZvaWNlbWFpbDogNDE2MzAzOTkyMw0K
`
end



  reply	other threads:[~2010-07-29  0:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-28 20:20 [gentoo-user] dir is rwx but can't create file Andrey Vul
2010-07-28 20:52 ` Alan McKinnon
2010-07-28 22:11   ` Bill Longman
2010-07-29  0:23     ` Andrey Vul [this message]
2010-07-29 12:56       ` [gentoo-user] " Andrey Vul
2010-07-29 13:00         ` Andrey Vul
2010-07-29 11:24 ` walt
2010-07-29 12:10   ` Alan McKinnon
2010-07-29 12:31   ` Alex Schuster
2010-07-30  5:34     ` Andrey Vul
2010-07-30  5:37       ` Andrey Vul

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=AANLkTik_cpGZSZMbh1g+0AkibiV6BfJXvDgLzZghkUhs@mail.gmail.com \
    --to=andrey.vul@gmail.com \
    --cc=gentoo-user@lists.gentoo.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