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