Loosing perrmissions to write.

[lord_t]

Hi,

first, sorry for my English
second, my problem:

I'm using hardy, writing some program using Qt4, and after few minutes/hours I'm loosing permissions to write on disk.

Maybe You know what is doing that?


P.S. I also notice that when I'm shutting down kubuntu it starts to close, but then I see (fullscreen) console and field to login in it.

[flarson]

Re: Loosing perrmissions to write.

Your filesystem is probably remounting itself read-only because it detects a hardware error. look in /var/log/syslog and you will probably see messages. The stopping at a VT is something I have been seeing lately also. I thought it might have to do with the Nvidia drivers but I have not found the solution yet.

[lord_t]

Re: Loosing perrmissions to write.

Thanks, i found some information there:

Mar 26 22:30:26 lord-laptop kernel: [  28.721888] EXT3-fs: INFO: recovery required on readonly filesystem.
Mar 26 22:30:26 lord-laptop kernel: [  28.721894] EXT3-fs: write access will be enabled during recovery.
Mar 26 22:30:26 lord-laptop kernel: [  32.111688] kjournald starting. Commit interval 5 seconds
Mar 26 22:30:26 lord-laptop kernel: [  32.111706] EXT3-fs: hda2: orphan cleanup on readonly fs
Mar 26 22:30:26 lord-laptop kernel: [  32.111713] ext3_orphan_cleanup: deleting unreferenced inode 1606383
Mar 26 22:30:26 lord-laptop kernel: [  32.111762] EXT3-fs: hda2: 1 orphan inode deleted
Mar 26 22:30:26 lord-laptop kernel: [  32.111764] EXT3-fs: recovery complete.
Mar 26 22:30:26 lord-laptop kernel: [  32.132584] EXT3-fs: mounted filesystem with ordered data mode.

This is it? What could makes that?



Full syslog:http://lord.psary.net.pl/hornet/linux_rescue/syslog.txt

[flarson]

Re: Loosing perrmissions to write.

Actually that is a fairly normal message from an ext3 filesystem being mounted. It first checks itself and then mounts. It is interesting that it found an orphaned inode though, that is filesystem corruption.

I think what caused your disk to be remounted read-only happened before that. Try looking at syslog.0, or syslog.1 until you find a message about remount read-only.

[lord_t]

Re: Loosing perrmissions to write.

I looked up and I don't see anything like you wrote.

syslog.0

[flarson]

Re: Loosing perrmissions to write.

How do you know you have lost write permission?

Do you have a full hard disk?
df -h will shoud you how much disk you have available and used.

does this happen often? please post the command you try to run and the message you get.

[lord_t]

Re: Loosing perrmissions to write.

I didn't write until today, because that strange behaviour disappeared.

Today I was writing in Kate and when I want to save, I saw alert:
(translating
The document could not be saved because you can not write to file: / / / home / lord / izograf / mod_liczacy.cpp.
Make sure you have write access to the file or whether there is enough space on the disk.

I can't use df -h (console isn't work correct), but there is about 20GB free space.

I tried to login root:

lord@lord-laptop:~$su
bash: /bin/su: Input/Output error

Also I tried to open folerd (Data storage device) but there was alert:
You can not start process Unable to create io-slave: Read-only file system.

[flarson]

Re: Loosing perrmissions to write.

I am almost sure you have a disk that is giving trouble. Depending on how many disks you have and which one is failing you might get some log info, but not if the log is on the failing disk. If you can run commands as root you might try to remount it. If the hardware problem has subsided it will remount and you will be in operation, for a little while. You need to be looking at backing up anything on that disk you do not want to lose.

[toad]

Re: Loosing perrmissions to write.

I concur. Try a

touch 1234

in your home. That creates a file called 1234. If you can't do it, do a reboot and see whether the problem persists.

[lord_t]

Re: Loosing perrmissions to write.

Thanks for help mando_hacker.