Now that it has been rebooted, are you still unable to create the
directory or write to it's parent?  In other words, has the issue been
resolved by rebooting?

>From that mount command output, it appears that while /var/run and
/var/lock are using tmpfs in their own mount path, the prime /var
directory looks to be in the same filesystem as / (and it is set to
remount as RO if there are any errors.)

Just as a side comment (not recommending you change it but an
opportunity to learn something...)   Having /var share a filesystem with
/ (where /root logs into, and where /etc are rooted, etc.) isn't the
best configuration if the server is also acting as a server that accepts
content over remote connections, such as an ftp or smtp server which
write content into /var/spool or similar directories, but it could be OK
in this customers case as they may not have any public facing services
(I have no idea)



On 10/26/2011 10:27 AM, Ann wrote:
> David,
> Well they brought the server back up.  Here is the result of the mount
> command
> 
> /dev/sda1 on / type ext3 (rw,errors=remount-ro)
> proc on /proc type proc (rw)
> /sys on /sys type sysfs (rw)
> varrun on /var/run type tmpfs (rw)
> varlock on /var/lock type tmpfs (rw)
> udev on /dev type tmpfs (rw)
> devpts on /dev/pts type devpts (rw,gid=5,mode=620)
> devshm on /dev/shm type tmpfs (rw)
> lrm on /lib/modules/2.6.15-51-386/volatile type tmpfs (rw)
> 
> which is very close to what my other servers look like with the
> exception of this line:
> securityfs on /sys/kernel/security type securityfs (rw)
> 
> What do you think?
> thanks
> Ann
> 
> 
> David Kaiser wrote:
>> It's hard to imagine, but...  is the /var filesystem mounted readonly?
>> The error doesn't look like directory permissions, but filesystem issues.
>>
>> run the 'mount' command and inspect any filesystems with a portion of
>> '/var/' in the mountpath, and/or do not contain 'rw' in the mount options.
>>
>>
>>
>> On 10/26/2011 09:43 AM, Ann wrote:
>>   
>>> I have a customer with an ubuntu linux server.  Last time I made any
>>> changes for him was in July.  Now when I go to copy anything to the
>>> server I get the following:
>>>
>>> cp: cannot create directory
>>> `/var/lib/tomcat5/backups/Infoportal_test_20111026_0936': Read-only file
>>> system
>>>
>>> It looks like something must have changed, but we have not done anything
>>> and I am pretty sure neither has he.  Any thoughts?
>>>
>>> I am signed in as root (please don't give me a lecture)
>>> thanks
>>> Ann Richmond
>>>
>>>     
>>
>> _______________________________________________
>> LinuxUsers mailing list
>> LinuxUsers@socallinux.org
>> http://socallinux.org/cgi-bin/mailman/listinfo/linuxusers
>>
>>
>>   
> 
> -- 
> Ann Richmond
> ----------------
> Randr Inc
> 951-369-3427
> 951-787-8683 Fax
> www.randrinc.com
> 
> 
> 
> _______________________________________________
> LinuxUsers mailing list
> LinuxUsers@socallinux.org
> http://socallinux.org/cgi-bin/mailman/listinfo/linuxusers

_______________________________________________
LinuxUsers mailing list
LinuxUsers@socallinux.org
http://socallinux.org/cgi-bin/mailman/listinfo/linuxusers

Reply via email to