While /tmp's mode is 1777, it doesnt make a difference since the same error occurs with /etc, /lib32, and /var.
On 2010-07-29, Andrey Vul <andrey....@gmail.com> wrote: > Also, echo > /tmp/foo => same thing > It looks like a problem with open(..., O_CREAT|O_TRUNC, 644), but i'll > retry strace'ing the open,write and see where the problem chain starts > > On 2010-07-29, Andrey Vul <andrey....@gmail.com> wrote: >> If / was mounted ro, touch would output strerror(EROFS), not >> strerror(ENOENT) >> >> On 2010-07-28, Bill Longman <bill.long...@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 >> > > -- > Sent from my mobile device > > Andrey Vul > begin-base64 600 sig > bXNuLCBob21lOiBhbmRyZXkudnVsQGdtYWlsLmNvbQ0KdSBvZiB0OiBhbmRyZXkudnVsQHV0b3Jv > bnRvLmNhDQpzbXMsIHZvaWNlbWFpbDogNDE2MzAzOTkyMw0K > ` > end > -- Sent from my mobile device Andrey Vul begin-base64 600 sig bXNuLCBob21lOiBhbmRyZXkudnVsQGdtYWlsLmNvbQ0KdSBvZiB0OiBhbmRyZXkudnVsQHV0b3Jv bnRvLmNhDQpzbXMsIHZvaWNlbWFpbDogNDE2MzAzOTkyMw0K ` end
