| 1 |
If / was mounted ro, touch would output strerror(EROFS), not strerror(ENOENT) |
| 2 |
|
| 3 |
On 2010-07-28, Bill Longman <bill.longman@×××××.com> wrote: |
| 4 |
> On 07/28/2010 01:52 PM, Alan McKinnon wrote: |
| 5 |
>> On Wednesday 28 July 2010 22:20:17 Andrey Vul wrote: |
| 6 |
>>> Creating files in /tmp, /etc, /lib32, and /var return ENOENT (touch |
| 7 |
>>> /tmp/foo => strerror(ENOENT)). |
| 8 |
>>> However, this is done as root and the dirs are marked 755 root:root. |
| 9 |
>>> df -i shows only 2% inode usage. |
| 10 |
>>> Any explanation as to why a rwx-ed dir can't be written to? This is |
| 11 |
>>> breaking quite a few of the init scripts. |
| 12 |
>>> |
| 13 |
>>> -- |
| 14 |
>>> Andrey Vul |
| 15 |
>>> begin-base64 600 sig |
| 16 |
>>> bXNuLCBob21lOiBhbmRyZXkudnVsQGdtYWlsLmNvbQ0KdSBvZiB0OiBhbmRyZXkudnVsQHV0b3J |
| 17 |
>>> v bnRvLmNhDQpzbXMsIHZvaWNlbWFpbDogNDE2MzAzOTkyMw0K |
| 18 |
>>> ` |
| 19 |
>>> end |
| 20 |
>> |
| 21 |
>> sounds like / is mounted read-only |
| 22 |
> |
| 23 |
> Do read-only filesystems typically reply ENOENT when trying to create a |
| 24 |
> file? It's usually something like "read-only filesystem" in that case. |
| 25 |
> ENOENT means it can't even find the file. |
| 26 |
> |
| 27 |
> |
| 28 |
|
| 29 |
-- |
| 30 |
Sent from my mobile device |
| 31 |
|
| 32 |
Andrey Vul |
| 33 |
begin-base64 600 sig |
| 34 |
bXNuLCBob21lOiBhbmRyZXkudnVsQGdtYWlsLmNvbQ0KdSBvZiB0OiBhbmRyZXkudnVsQHV0b3Jv |
| 35 |
bnRvLmNhDQpzbXMsIHZvaWNlbWFpbDogNDE2MzAzOTkyMw0K |
| 36 |
` |
| 37 |
end |
Archives